Hi!
6-Янв-2005 23:47 [EMAIL PROTECTED] (Peter Fedorow) wrote to
[email protected]:
>>>> OmmitIfOptimizeSize break ();
>> Very hard to justify such macros, then you may as well use a comment, the
>> potentially nasty fallthrough would still be there in the "embedded case".
PF> A macro will allow all such cases to be turned on and off at once. This
There is no noticeable gain (in resulting code size) and no enhancement
of source, so such places better to optimize "at all" and just comment
tricky places (for example, where reused `break' from following `case'
branch).
PF> A more accurate name for the macro would probably be
PF> OmmitIfOptimizeSizeExtreme, but I think that might be getting
PF> rediculously long. Perhaps someone has a better name for it?
Again: better to not bother with _such_ ways, just optimize. And
comment tricky places.
>> IMHO if you really want to save space for embedded stuff you should
>> selectively remove features (e.g. FAT12 or FAT32, LBA, FCB stuff,
>> whatever). Those in the business hopefully make money of their embedded
>> stuff, and they are free to make such modifications; they should not prey
>> to the kernel developers to do it.
PF> Are embedded developers welcome to send in clean patches to selectively
PF> remove those items?
To remove - no. To send patches, which _adds_ possibility of
conditional compilation (with removing some unneeded parts) - yes.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Freedos-kernel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
