this post was submitted on 08 Jul 2026
49 points (98.0% liked)
Programming
27631 readers
167 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I once worked on a project where a third party-parser had a bug that effectively made it sensitive to the order it loaded files.
This wasn't a syntactic or a semantic problem. There was a stack processing issue that could be avoided by simply loading the files in a different order. This might have changed the final semantics if one file contradicted another, but that generally didn't happen. Each file had a specific purpose and it would still break without any contradictions.
The default load order was whatever order the file system had the files stored, but knowing that wouldn't necessarily help because changing the size or contents of a file in such a way that it retained the same position might trigger the same issue. Therefore you could force by-Unicode load ordering and still have it choke.
It was very hard to track down and I very much did not like editing those files for fear of triggering the parser bug. When I had to would be where the regret kicks in.
The other regret, and maybe a little more relevant, was renaming all the files to a different filename format that didn't make any difference in the end, but it was uglier than the original and it stuck.
I believe a later version of that parser fixed the bug(s), but I moved on.