Menu
▾
▴
Re: [MACTCL] tkConfig.sh
|
From: Jim I. <ji...@ap...> - 2001-10-19 17:44:49
|
Jack, For Carbon, Apple distributed "flat headers" along with the Frameworks. So, in some standard place they put headers that just routed the standard include over to the framework style include. So you would have a tcl.h that just includes <Tcl/tcl.h>. Another way to go? Jim On Friday, October 19, 2001, at 05:49 AM, Jack Jansen wrote: > >>> I am not sure whether is is best to work this into configure or do it >>> as a post-processing step. I was planning tenatively to do the >>> "#include <Tcl.h>" -> "#include <Tcl/Tcl.h>" when I moved the headers >>> into the framework, [...] > > For Python we have decided not to do this, at least, not yet. > > While Apple's "#include <Tcl/Tcl.h>" framework solution is really > elegant it > is also completely private to MacOSX (before I get thrashed, okay, > okay, it > probably comes from NeXT:-). > > Unless you can convince the whole Tcl/Tk world to switch to the > Tcl/Tcl.h > convention (and preferrably retroactively, say about 5 years ago:-) you > will > forever haunt the Tcl/Tk community with extensions that were created on > OSX > and won't compile on anything else, or the other way around. > > While the Tcl/Tcl.h convention is really elegant in that it forestalls > name > clashes in header files, given the fact that most of the software out > there > uses unadorned include files I think apple should add a > "-compat-framework" > option or some such that would allow #include "Tcl.h" to work, giving > compatibility at the expense of potential name clashes. > -- > Jack Jansen | ++++ stop the execution of Mumia > Abu-Jamal ++++ > Jac...@or... | ++++ if you agree copy these lines to your > sig ++++ > www.cwi.nl/~jack | see http://www.xs4all.nl/~tank/spg- > l/sigaction.htm > > > > _______________________________________________ > Tcl-mac mailing list > Tc...@li... > https://lists.sourceforge.net/lists/listinfo/tcl-mac > -- Jim Ingham ji...@ap... Developer Tools - gdb Apple Computer |
