I'll note that when I convert code between languages, I often go out of my way to minimize on-the-fly refactoring, instead relying on a much more mechanical, 1:1 style. The result might not be idiomatic in the target language, but the bugs tend to be a bit fewer and shallower, and it assists with debugging the unfamiliar code when there are bugs - careful side-by-side comparison will make the mistakes clear even when I don't actually yet grok what the code is doing.
That's not to say that the code should be left in such a state permanently, but I'll note there's significantly more changes in function structure than I'd personally put into an initial C-to-Rust rewrite.
The author of this rewrite appears to be taking a different approach, understanding the codebase in detail and porting it bit by bit, refactoring at least some along the way. Here's the commit that introduced that fn, doesn't look like automatic translation to me: https://github.com/Ragnaroek/iron-wolf/commit/9014fcd6eb7b10...
yndoendo 7 hours ago [-]
I actually find 1:1 to be helpful when learning a language.
How debug-able is the internals of the rust lambda version?
I will often write the code so I can simply insert a break point for debugging versus pure anonymous and flow-style functions.
As a non-Rust guy, I keep writing the example above. I didn't even know about the second option!
If you do that, please share a link so I can learn from you! This is awesome!
DauntingPear7 18 hours ago [-]
Look into rust iterators and their associated functions for rust specific implementation. Additionally look into functional programming à la lambda calculus and Haskell for the extreme end of this type of programming if you’d like to learn more about it
ragnaroekX 1 days ago [-]
Yes, the code is _very, very_ close to the C-Code. All over the place.
derwiki 1 days ago [-]
Sounds like something an LLM agent might be good at?
ragnaroekX 15 hours ago [-]
It probably would.
But this port was mostly done to understand Wolfenstein 3D in detail, not for the source port itself.
I could have generated big parts of the code. But I would have learning by doing that.
amelius 1 days ago [-]
Wolfenstein is peanuts compared to writing your own doubly linked list.
1 days ago [-]
yuppiepuppie 1 days ago [-]
This is cool! Wolfenstein will always have a place in my heart.
Stein means rock. Wolfenstein is something like Wolf’s rock.
Eisen means Iron. You could name it Wolfeneisen?
hamza_q_ 1 days ago [-]
Cool! I did an incomplete version in Rust a while back as well. Not a source port, tried to recreate the game from scratch myself, without looking at the C src code
Wolfenstein 3D was pretty squarely a WWII fantasy shooter. Only later does it get into the alternate history post-war stuff which does get somewhat more squarely political.
I think it cuts both ways. The Wolfenstein franchise has obviously relished in violence against Nazis, but also inadvertently is part of the trend of glorifying them.
TehCorwiz 1 days ago [-]
The first game has zombies with guns in their chest and a mecha hitler.
bombcar 24 hours ago [-]
Someone's not up to date on the History Channel documentaries about WWII!
> Was this translated automatically from C?
I'll note that when I convert code between languages, I often go out of my way to minimize on-the-fly refactoring, instead relying on a much more mechanical, 1:1 style. The result might not be idiomatic in the target language, but the bugs tend to be a bit fewer and shallower, and it assists with debugging the unfamiliar code when there are bugs - careful side-by-side comparison will make the mistakes clear even when I don't actually yet grok what the code is doing.
That's not to say that the code should be left in such a state permanently, but I'll note there's significantly more changes in function structure than I'd personally put into an initial C-to-Rust rewrite.
The author of this rewrite appears to be taking a different approach, understanding the codebase in detail and porting it bit by bit, refactoring at least some along the way. Here's the commit that introduced that fn, doesn't look like automatic translation to me: https://github.com/Ragnaroek/iron-wolf/commit/9014fcd6eb7b10...
How debug-able is the internals of the rust lambda version?
I will often write the code so I can simply insert a break point for debugging versus pure anonymous and flow-style functions.
C# example:
vsIf you do that, please share a link so I can learn from you! This is awesome!
You should add it to https://hnarcade.com
Eisen means Iron. You could name it Wolfeneisen?
https://github.com/hamzaq2000/wolf3d-reimpl-rs
https://steamcommunity.com/app/612880/discussions/0/14708409...
https://www.newstatesman.com/science-tech/2017/06/alt-right-...
I think it cuts both ways. The Wolfenstein franchise has obviously relished in violence against Nazis, but also inadvertently is part of the trend of glorifying them.
- Once started the shareware game on Chromium browsers seems to flicker like crazy which displays the "B.J. Blazkowicz" face.
- You missed adding the classic code that everyone knows, M-L-I!
I did a WASM port of the shareware from https://github.com/fabiangreffrath/wolf4sdl playable at https://midzer.de/wasm/wolfenstein/
Port it to 286, and then claim RUST victory