🚀 go-pugleaf

In article <keithley-181292171536@kip2-37.apple.com>, keithley@apple.com
(Craig Keithley) wrote:
> 
> Tools can have command line options and so forth. 
> Custom tools (cross compilers & assemblers), scripts, and projector are the
> reasons why I don't use Think C.  I build a software pack
> 

And I seem to have trailed off.  I guess I posted the wrong file.  Here's
what I was trying to say:  The result of the build process is a single file
(binary or S-record) that contains object code for 680xx and non-680xx
processors.  One file, two or three different processors.

Sorry about that fade-out.

In article <BzHqzF.D7w@acsu.buffalo.edu>, okeefe@cs.Buffalo.EDU (Paul
O'Keefe) wrote:
> 
> 
> So, I suspect that it's Apple's conservative legal policy and not the copyleft
> that prevents Craig from using GCC.
> 

Its very important that you don't take my non-use of the GNU tools as an
indication that you shouldn't use said tools.  I've heard really good
things about the GNU suite of tools, and under different circumstances, I'd
probably use them myself.  

But I stand by my suggestion that you carefully read the GNU documents
(especially for GCC & Bison) before using or porting GNU tools.  This
suggestion  holds true for any software development tool.  These days, with
run-time licenses, copyrights, copylefts, and so forth, its very important
that the software developer understand her or his rights, responsibilities,
and liabilities.


Craig Keithley
Apple Computer, Inc.
keithley@apple.com
"I have absolutely no responsibility in this matter, what-so-ever"