Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!sri-spam!ames!ucbcad!ucbvax!decvax!dartvax!earleh
From: earleh@dartvax.UUCP (Earle R. Horton)
Newsgroups: comp.sys.mac
Subject: Re: Broken compilers
Message-ID: <6186@dartvax.UUCP>
Date: Wed, 13-May-87 01:20:15 EDT
Article-I.D.: dartvax.6186
Posted: Wed May 13 01:20:15 1987
Date-Received: Sat, 16-May-87 07:46:52 EDT
References: <949@batcomputer.tn.cornell.edu> <746@apple.UUCP> <1953@husc6.UUCP>
Organization: Society for the Prevention of Cruelty to Graduate Students
Lines: 19
Keywords: IMPORTANT WARNING LIGHTSPEED C
Summary: Some clarification, please.

In article <1953@husc6.UUCP>, stew@endor.harvard.edu (Stew Rubenstein) writes:
> 
> All programs compiled with LightSpeed C WILL BREAK, GUARANTEED 100%,
> when Apple comes out with a 32 bit operating system for the Mac II or
> future hardware.  This is true of LightSpeed C versions 1.02 and 2.01.
> The problem is that they use a BSET instruction to manipulate Handle
> state flags.  Apple has repeatedly warned Developers (e.g., in Tech
> Note #2, dated January 21, 1986) that this is a no-no.

Is this a general compiler problem, or is it, rather, specific to some
of the runtime libraries?  The above explanation does not make this
clear.  I would appreciate some detail as to where the offending BSET
instruction gets inserted into the typical C program.  In particular,
does a program using only "MacTraps" have this problem?

-- 
****************************************************************************
*  Dot seegnachur?  I don' got to show you no steenkeen dot seegnachur!!   *
****************************************************************************