🚀 go-pugleaf

Jacob Parnas, from IBM Thomas J. Watson Research Center writes:
| Charlie Slater, Eric Brunner, and Jeff Weinstein at IBM Palo Alto have
| been very helpful in helping to fix the few problems that we have had.

Based on my experience, what you say makes me suspect that Yorktown
Heights gets, ummm, slightly better service than we do.  Maybe that's
not surprising. :-)

I think very highly of the people from IBM Palo Alto that I've met.
The problem is that we have to deal with USC/ACSC as the middleman.

| ... the C compiler among other parts of the OS have been greatly 
| improved).

Errr.  The unwashed masses are holding their breath waiting for the
gcc port.  Let me be as blunt as I can: I won't use "hc" for anything
that actually needs to work.  This is not a flame, just a frightened
observation.

We'll see about the new release (2.1s) as soon as it is installed.  My
first test program will look like this:

#ifdef __STDC__		/* Oh good, a 100% ANSI conforming compiler! */
#define FOO(x) #x
static char foo[] = FOO(bar);
			/* should expand to ``static char foo[] = "bar";'' */
#endif

All previous releases of hc get this wrong; they fail to compile it.

| I highly recommend trying 4.3 AOS, if it is available to you.

Agreed.  Get real unix while you still can.

disclaimer: I'm just a grad student and my opinion doesn't count for anything.
--
Scott Schwartz		<schwartz@shire.cs.psu.edu>
"APAR's?  We don' neeed no steeenking APARS!"