squeek502

hace 2 mesesdiscuss

Might not make it in time for 0.17 but there is a contributor making progress on the COFF linker: https://codeberg.org/kcbanner/zig/src/branch/coff_linker_wip

squeek502

hace 8 mesesdiscuss

That would only interact with the shell, as `%` is not actually part of the environment variable name, it's just a way to tell the shell you want it to get the value of an environment variable. The environment block itself is a NULL terminated list of NULL terminated WTF-16 strings of the format <key>=<value>, so `=` would be the more interesting thing to try.

And indeed, it looks like using `=` as a drive letter breaks things in an interesting way:

    =:\> cd bar
    Not enough memory resources are available to process this command.

    =:\bar>

`cd` exits with error code 1, but the directory change still goes through.

With a program that dumps the NULL terminated <key>=<value> lines of the environment block, it looks like it does still modify the environment, but in an unexpected way:

Before `cd /D =:\`, I had a line that looked like this (i.e. the per-drive CWD for C:\ was C:\foo):

    =C:=C:\foo

After `cd /D =:\`, that was unexpectedly modified to:

    =C:==:\

Funnily enough, that line means that the "working directory" of the C drive is `=:\`, and that actually is acted upon:

    =:\foo> cd /D C:

    =:\>

---

You might also be interested to know that '= in the name of an environment variable' is a more general edge case that is handled inconsistently on more than just Windows: https://github.com/ziglang/zig/issues/23331

squeek502

hace 8 mesesdiscuss

They work just fine, as the drive-specific CWD is stored in the environment as a normally-hidden =<drive-letter>: environment variable which has all the same WTF-16 and case-insensitive properties as drive letters:

    C:\> cd /D λ:\

    λ:\> cd bar

    λ:\bar> cd /D C:\

    C:\> echo %=Λ:%
    λ:\bar

    C:\> cd /D Λ:

    λ:\bar>

squeek502

hace 8 mesesdiscuss

> Any Mods you create for Minecraft: Java Edition from scratch belong to you (including pre-run Mods and in-memory Mods) and you can do whatever you want with them, as long as you don't sell them for money / try to make money from them

https://www.minecraft.net/en-us/eula

squeek502

hace 11 mesesdiscuss

0.15.0 was effectively skipped: https://github.com/ziglang/www.ziglang.org/commit/1be0f80b15...

squeek502

el año pasadodiscuss

Good catch, that does indeed look like a mistake in the spec. Everything past the first sentence of that error description is suspect, honestly (seems like it was naively adapted from the example in [1] but that example isn't relevant to the missing-semicolon-after-character-reference error).

Will submit an issue/PR to correct it when I get a chance.

[1] https://html.spec.whatwg.org/multipage/parsing.html#named-ch...

squeek502

el año pasadodiscuss

Appreciate it (I'm the author). I'd like to think there's a good bit of interesting stuff in here outside of the specific topic of named character reference tokenization.

squeek502

el año pasadodiscuss

FWIW here's what that looks like for Zig: https://ziglang.org/news/2024-financials/

squeek502

el año pasadodiscuss

Relevant: https://github.com/ziglang/zig/issues/4055#issuecomment-1646...

squeek502

el año pasadodiscuss

As far as I'm aware, using the self-hosted backend for anything other than Debug mode is a goal, but a far-future goal.

I believe the most relevant links are https://github.com/ziglang/zig/issues/16270 and https://github.com/orgs/ziglang/projects/2/views/1?pane=issu... (as you can see, nothing is concrete yet, just vague mentions of optimization passes)

squeek502

el año pasadodiscuss

I'm probably not describing it fully accurately. See the link for the proper explanation.

squeek502

el año pasadodiscuss

My understanding is that Zig's incremental compilation will work on a much more granular level (i.e. functions, etc), so, for example, change one function and only that function (and its dependencies) will get recompiled/relinked (there's some linker trickery involved to avoid needing to relink everything IIUC).

More details here: https://ziggit.dev/t/how-zig-incremental-compilation-is-impl...

squeek502

hace 2 añosdiscuss

For the miscompilations, the fix wouldn't add a new compile error. Instead, rc.exe would just start doing the right thing in certain scenarios, so previously broken things would start working. For example, padding bytes that were previously missing would get properly added.

It's always theoretically possible that someone, somewhere is somehow relying on such a miscompilation, but for many of the ones detailed in the article, it seems extraordinarily unlikely.

squeek502

hace 2 añosdiscuss

I think everything labeled 'miscompilation' could be fixed without breaking backwards compatibility, since triggering them always leads to an unusable/broken .res file. No clue how likely it is they'll be fixed, though.

squeek502

hace 2 añosdiscuss

See https://www.ryanliptak.com/blog/zig-is-a-windows-resource-co... for an example of using the Zig build system to cross-compile an existing Windows GUI program written in C from any supported host system.

squeek502

hace 2 añosdiscuss

Apologies if I got the tone wrong there, I definitely wasn't trying to roast the other projects.

In terms of what I prioritized bug-for-bug compatibility on, I tailored it to getting https://github.com/squeek502/win32-samples-rc-tests passing 100%, and then also tried to take into account how likely a bug/quirk was to be used in a real .rc file (ultimately this is just a judgement call, though). The results of that test suite (provided in the readme) is also a better indication of how rc.exe-compatible the various resource compilers are in practice (i.e. on 'real' .rc files).

squeek502

hace 2 añosdiscuss

Appreciate the added context!

> |-separated lists of numeric or NOT

Note that | is not the only operator that can be used in style parameters, & + and - are all allowed too.

> perhaps Windows versions that don't support DIALOGEX also don't support GROUPBOX

Seems possible for sure. From [1]:

> The 16-bit extended dialog template is purely historical. The only operating systems to support it were the Windows 95/98/Me series.

[1] https://devblogs.microsoft.com/oldnewthing/20040622-00/?p=38...

> The examples below this also seem to have reversed the order of the input byte and the FF.

Good catch, fixed

squeek502

hace 2 añosdiscuss

Thanks!

I'm actually pretty okay with where I've landed with FONT resources. The legwork has already been done in figuring things out, and with the strategy I've chosen, resinator doesn't even need to parse .fnt files at all, so the implementation is pretty simple (I wrote a .fnt parser, but it's now unused[1]).

[1] https://github.com/squeek502/resinator/blob/master/src/fnt.z...

squeek502

hace 2 añosdiscuss

I'm the author if anyone has questions

squeek502

hace 2 añosdiscuss

All of the listed goals have arguably been met, except:

- Auto-generating a `.h` file has temporarily regressed

- Friendly toward package maintainers is an ongoing goal

- "Memory zeroed by default" is not accurate, instead you must initialize all variables (to either some value or `undefined`)

Submissions

Zig is now also a Windows resource compiler

Fuzzing as a Test Case Generator

Rampsliding Is a Quake Engine Quirk in the Same Way That Bunnyhopping Is

Rampsliding Is a Quake Engine Quirk in the Same Way That Bunnyhopping Is

Rampsliding Is a Quake Engine Quirk in the Same Way That Bunnyhopping Is

comments