current winsup/cygwin/*.h files policy

Egor Duda deo@logos-m.ru
Wed Dec 6 11:54:00 GMT 2000


Hi!

Wednesday, 06 December, 2000 Christopher Faylor cgf@redhat.com wrote:

>>  if   i  understand  correctly,  *.h  files  in  winsup/cygwin/  were
>>redesigned   some  time  ago  from   single  monolithic  winsup.h to a
>>bunch of small *.h files which don't use
>>#ifndef _FOO_H_
>>#define _FOO_H_
>>...
>>#endif
>>construct,   and   should   be   included  in  *.cc  files  in correct
>>order  to satisfy all dependencies.  there're,  however  4  *.h  files
>>left,   which   include   other   "*.h"  files  --  heap.h,  pinfo.h,
>>shared_info.h and winsup.h.  was it intentional?

CF> Yes.  I'm not trying to be overly dogmatic about this.  If it makes sense
CF> to include perthread.h in thread.h, then go ahead and do that.  Just make
CF> sure that you remove any duplication from any source files.

ok.

>>btw, does usage of c++'s multiple inheritance allowed in cygwin?

CF> I'm not sure what you mean.  Aren't some fhandler classes doing this already?

no.  'grep  "class.*:.*,.*"  *'  shows only lines in ChangeLogs. i was
meaning  that  cygwin used to avoid some g++ features (-fno-exceptions
-fno-rtti),  so  i wanted to make sure that multiple inheritance is ok
in current gcc.

Egor.            mailto:deo@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19




More information about the Cygwin-developers mailing list