Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!decwrl!ucbvax!BRILLIG.UMD.EDU!fred
From: fred@BRILLIG.UMD.EDU.UUCP
Newsgroups: mod.computers.pyramid
Subject: Re: System V Pic command on 90x
Message-ID: <8606110456.AA00995@brillig.umd.edu>
Date: Wed, 11-Jun-86 01:47:42 EDT
Article-I.D.: brillig.8606110456.AA00995
Posted: Wed Jun 11 01:47:42 1986
Date-Received: Wed, 11-Jun-86 18:59:21 EDT
References: <8606062053.AA04670@rayssd.UUCP>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 33
Approved: info-pyramid@mimsy.umd.edu


	From: seismo!allegra!rayssd!rayssde!wjc@mimsy.umd.edu

	We are running 4.2BSD on a 90x and are having a problem
	getting System V Pic going. The problem seems to be in the
	program troffgen.c. Instead of passing all the troff commands
	(ie. .ps, .vs, .anything) to troff, it is printing a "ctrl A"
	instead.  Has anyone had any luck with Pic????? Any help
	would be appreciated.

					Bill Carson
					{allegra,ihnp4,linus}!rayssd!wjc

This isn't specific to ``pic'', but it sounds awful similar to a
problem I had transporting a piece of software from a VAX to the
Pyramid. It seems that on a VAX, there is always a null byte at
address 0, while on the Pyramid there's a ^A at 0, and a null byte
at address 1. This lets one get away, on the VAX, with some sloppy
programming:

	char *splat;

	splat = (char *)0;
	printf("%s", splat);

This will do ``the right thing''; that is: it will print nothing.
If this sort of thing is allowed to creep into your code and you
then transport it to a Pyramid, you start getting mysterious ^As
popping up unexpectedly.
----
					Fred Blonder (301) 454-7690
					seismo!umcp-cs!fred
					Fred@Mimsy.umd.edu