🚀 go-pugleaf

With regards to the SC 6.1 release:
From article <137@titania.warwick.ac.uk>, by cudcv@warwick.ac.uk (Rob McMahon):
> The first [problem] is the ctl macro relies on a non-ANSI
> pre-processor which will do replacement of macro arguments within
> strings, this will stop it compiling at all.

This release has been interesting from this perspective.  The ctl()
macro has been "shipping" like this for 3+ years and I have never had a
complaint before now.  I have received at least 5 separate complaints
since the 6.1 release last month.  I draw a couple of conclusions - gcc
is a real force in the market and ANSI is breaking some things they
should have standarized.

I will fix this in the next release.   If I get enough other bug
reports and I have the time (not likely before May), I may send out a
patch.  

> The second is that it tries to write to strings constants, which may be
> in read-only memory, so that it dumps core as soon as you try to run it.

Who said compilers could put strings somewhere other than data space?  :-)

						Bob