I agree. However it's not nice to move files in CVS, even with all the
howtos, and I don't like that later we may have to move emulator.h, js.h,
or mapper.h. I know that seams unlikely but if we bend slightly we should
be prepared to break and prepend "_" to every ".h". copy/link gives us
the abbility to do that /wo having to wory about messing with CVS
internals. Also this could just be a win32 thing, I don't mind having
#ifdevs around includes. In that we only have to move the files when we
need to.
--- Jason Dorje Short <jd...@us...> wrote:
> Mike Mestnik wrote:
> > copys or hardlinks can be made and on systems where it's an issue the
> old
> > name can be removed.
> >
> > --- Jason Dorje Short <jd...@us...> wrote:
> >
> >>I still have a problem compiling for win32 whereby tuxnes's "io.h" is
> >>included instead of the system's <io.h>.
> >>
> >>This is very confusing to me.
> >>
> >>1. dirent.h has an '#include <io.h>'. The use of <> here should mean
>
> >>system headers are included before local headers.
> >>
> >>2. Of course there's a <types.h> as well as a "types.h". But we
> don't
> >>seem to have problems here.
>
> For the record, I strongly feel renaming or linking files at compile
> time is a very bad idea.
>
> On the other hand, renaming files for no reason is also a bad idea.
>
> So we need to get to the bottom of this and find out _why_ the current
> method fails.
>
> jason
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to
> deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Tuxnes-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxnes-devel
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
|
