Re: [Tuxnes-devel] io.h

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

Mike Mestnik wrote:
> I have thouight long and hard about this.  There are some things I don't
> like.
> 
> 1. Losing history in CVS.

This is annoying.  But note it's not lost, just much harder to access. 
Also note the file is only two lines long :-).

> 2. Having to avoid names for .h files in our parent object.  Listing what
> names we can't use is just plain wrong IMHO.

Yep.  Tuxnes also has a types.h which is a header file, but this doesn't 
cause problems.  I don't know why.

> 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.

Anything will do.  It would be better just to rename.

> 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.

I'm not quite sure what you're saying here.

> 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.

I think the build system (or maybe the global header files) must be 
wrong somewhere.  This *shouldn't* be a problem.  But I haven't been 
able to find the problem yet.

jason