Path: utzoo!mnetor!uunet!steinmetz!ge-dab!codas!usfvax2!pollock
From: pollock@usfvax2.UUCP (Wayne Pollock)
Newsgroups: comp.sys.mac
Subject: Re: sprintf() bug?
Message-ID: <951@usfvax2.UUCP>
Date: 6 Feb 88 06:33:32 GMT
References: <4VzXREy00WABE7k0FU@andrew.cmu.edu> <5349@cit-vax.Caltech.Edu> <943@cadre.dsl.PITTSBURGH.EDU> <1131@iscuva.ISCS.COM>
Reply-To: pollock@usfvax2.usf.edu.UUCP (Wayne Pollock)
Organization: University of South Florida at Tampa
Lines: 14
Keywords: C,sprintf,strings
Summary: What are the semantics of "\pstring"?

Funny; I thought for sure it would work.  I haven't tested it, but it would
seem to me that the \p is interpreted in some sort of glue routine, well after
the string is constructed.  That is, when a string containing "\p" is passed
to some toolbox routine, AT THAT TIME the length of the string is determined,
and substituted for the first byte.  If it works this way, then the example
given would indeed work as desired.

I'm not sure how it could work this way, unless LSC reserves some char code
(such as 255) as a marker; of course this would be incompatible with C syntax.
Anybody know for certain, or willing to crash his mac to check this out?

Wayne Pollock (The MAD Scientist)	pollock@usfvax2.usf.edu.UUCP
Usenet:		...!{ihnp4, cbatt}!codas!usfvax2!pollock
GEnie:		W.POLLOCK