Read the rest of the code extract... This isn't even close to being optimized. The only thing that's "optimized" is an "optimization" which breaks things. And then, people complain about my programs being unoptimized...
I wonder whether putting in the generic detection for the doorsos.h macros, and patching programs like Solar individually, is a reasonable solution...
PpHd Le 20/07/2004 à 09:27 Creating tifont.fonte at Preos startup, and search for it each time you run a kernel program (By temporary patching the font_medium value) ?
Or just throwing it into a locked handle in RAM? I don't want to keep reloading addresses which may move due to FlashROM garbage collection, and relying on that also subtly breaks any programs using both the fonts and anything in the archive.
PpHd Le 20/07/2004 à 10:28 >breaks any programs using both the fonts and anything in the archive.
Does such a program exists?
Probably. There are masses of kernel programs using those font hack RAM_CALLs.
), so these hacks are hardly a surprise, but still, why he didn't use the documented macros (which would be way easier to detect) is beyond me, especially given how the rest of the code is very far from being optimal anyway.
)
