Re: A C compiler written in C targeting C

zalman@netcom.com (Zalman Stern)
3 Apr 1999 21:59:27 -0500

          From comp.compilers
Related articles
[2 earlier articles]
Re: A C compiler written in C targeting C kadhim@lucent.com (Basim Kadhim) (1999-03-28)
Re: A C compiler written in C targeting C nshaf@intur.net (Nick Shaffner) (1999-03-28)
Re: A C compiler written in C targeting C dmk42@my-dejanews.com (1999-03-28)
Re: A C compiler written in C targeting C derek@knosof.co.uk (1999-03-28)
Re: A C compiler written in C targeting C eclectictech@usa.net (1999-03-28)
Re: A C compiler written in C targeting C dg@tao.co.uk (1999-04-01)
Re: A C compiler written in C targeting C zalman@netcom.com (1999-04-03)
Re: A C compiler written in C targeting C gillga@ilk.de (1999-05-16)
| List of all articles for this month |
From: zalman@netcom.com (Zalman Stern)
Newsgroups: comp.compilers
Date: 3 Apr 1999 21:59:27 -0500
Organization: ICGNetcom
References: 99-03-067 99-03-085
Keywords: C, storage

Actually, the funny thing is I've never seen such a tool for the
Mac. I think people felt it would be too inefficient vs. doing
explicit locking. Apple's 68k C++ compiler supported handle based
objects though. In effect all accesses to the object (e.g. this
relative references) were double indirected. You still occasionally
had to lock things due to the semantics of OS calls and the
possibility of asynchronous events.


-Z-




Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.