| www.delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
| Sender: | rich AT phekda DOT freeserve DOT co DOT uk |
| Message-ID: | <3C3DE9D2.6CBD2255@phekda.freeserve.co.uk> |
| Date: | Thu, 10 Jan 2002 19:21:54 +0000 |
| From: | Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk> |
| X-Mailer: | Mozilla 4.77 [en] (X11; U; Linux 2.2.19 i586) |
| X-Accept-Language: | de,fr |
| MIME-Version: | 1.0 |
| To: | djgpp-workers AT delorie DOT com |
| Subject: | Re: Proposed lstat.c patch for Win2000/XP device bit fix |
| References: | <200201091347 DOT OAA11490 AT lws256 DOT lu DOT erisoft DOT se> |
| Reply-To: | djgpp-workers AT delorie DOT com |
Hello. Martin Stromberg wrote: > > Charles said: [snip] > > + !strcmp(ff_blk.lfn_magic,"LFN32") && > > Isn't this code always included in the image. IIRC, the recommendation > is to use ff_blk.lfn_magic[0] == 'F' && ff_blk.lfn_magic[0] == 'A' && > ... if so. Why is this recommended? (I had a look through the thread, but I couldn't see the answer.) Surely the program size overhead of strcmp() vs. explicit comparison can't be that great. Also, I have a historical question: why was a 6 byte string magic field chosen, instead of some integer bitfield for options? Thanks, bye, Rich =] -- Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |