Re: [Tuxnes-devel] io.h problem

[Jason D. S. <jd...@us...>]

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