> Agreed, although we could use the symlink trick for all of the .H
> files to phase out .H in favor of .h (or create .H files that
> included the .h files after issuing a compile-time warning...)

I like the idea of switching to ".h", but providing ".H" wrappers -
means it will work on winXX and so forth, where symlinks won't play.

> Of course, the new "l33t" C++ header naming convention is to omit the
> extension entirely...

And lets not do that...



SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to