Re: [Tuxnes-devel] io.h
Brought to you by:
tmmm
From: Mike M. <che...@ya...> - 2004-03-16 03:50:52
|
I have thouight long and hard about this. There are some things I don't like. 1. Losing history in CVS. 2. Having to avoid names for .h files in our parent object. Listing what names we can't use is just plain wrong IMHO. 3. _ == tuxnes == just something you append to the front to avoid colistion with parent objects. _ is most popular, but this calles for tuxnes dosen't it. To over come losing history in CVS we can have the make system move the problem childern? To over come not knowing what problems we will have we will just live with it and fix on fail? We shal use tn_ or tn- as our new names? If this is aceptible I would requier check for my system so that cvs commit still workes, so the old names have to be conditionaly used. This check could be a genaric one for my system or it could only use the new names on systems where there is a problem. Once I have this I can create commit the fix. Also we should see what we can do about fixing the source of this bug. Althought I don't know anything about fixing broken build systems, so I could be wrong. --- Jason Dorje Short <jd...@us...> wrote: > The existance of io.h presents a problem when cross-compiling. io.h is > a needed header, and for some reason when the other headers #include > <io.h> it actually includes the local copy. Hence, compilation fails. > > I'd suggest renaming io.h to nesio.h. Maybe io.c should be renamed to > match. > > jason > __________________________________ Do you Yahoo!? Yahoo! Mail - More reliable, more storage, less spam http://mail.yahoo.com |