Re: [MACTCL] Carbon Dater Report on Tcl/Tk

[Jack J. <ja...@or...>]

I think "a few weekends" is probably overly optimistic for carbonizing tcl/tk, 
but it shouldn't be too difficult.

Just in case you're going to do this I'll give you some advice based on my 
experience carbonizing MacPython, feel free to ask for more info.

- portable software (like tcl or python) is a lot easier to carbonize than 
average software, because the dependencies tend to be localized.

- don't start with the easy bits, but start with looking at potential 
showstoppers. For MacPython this was the underlying GUSI I/O system, which 
used all asynchronous calls in a way that wasn't supported on Carbon. I had to 
wait for someone to port GUSI (at least partially) before I was able to 
proceed. Oh yes: the showstoppers will probably be in third-party libraries:-( 
Although in the case of tcl I think MoreFiles is the only one used, and that 
is available carbonized.

- Follow the order in Apple's Carbon Porting Guide. Especially the accessor 
stuff should be done early and globally (I didn't:-) as that keeps your 
program working under classic but allows you to do the bulk of the work 
(getting rid of lomem access and direct window/dialog/etc structure access).
--
Jack Jansen             | ++++ stop the execution of Mumia Abu-Jamal ++++
Jac...@or... | ++++ if you agree copy these lines to your sig ++++
www.oratrix.nl/~jack    | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm