Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucsd!hub!6600pete
From: 6600pete@ucsbuxa.ucsb.edu
Newsgroups: comp.lang.c
Subject: Re: Strings in C (Re: ambiguous ?)
Message-ID: <2742@hub.UUCP>
Date: 27 Oct 89 07:37:51 GMT
References: <11398@smoke.BRL.MIL> <14115@lanl.gov> <2522@munnari.oz.au>
	<6676@ficc.uu.net> <2421@convex.UUCP>
Sender: news@hub.UUCP
Reply-To: pete@cavevax.ucsb.edu
Organization: Underground BBS: rlogin 128.111.41.100 -l bbs
Lines: 26
In-reply-to: grogers@sushi.uucp's message of 26 Oct 89 13:36:04 GMT

In article <2421@convex.UUCP> grogers@sushi.uucp (Geoffrey Rogers) writes:
> In article <6676@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>>In most Macintosh C compilers that I've seen, the syntax !"%p...."! is

Actually, the syntax is "\p...", but that's only a nit I had to pick.

>>used to indicate byte-counted strings. P stands for "pascal".
>>
>>Was X3J11 aware of this? Or are the Mac compiler vendors going to change?

No, they're not. It's for ROM compatibility and there isn't a work-around.

> Why should Mac compiler vendors have to change this feature. It is an
> extension of the language, which they deem important for there market
> place.

Yes. But that seems so obvious as to not be an issue. (Although, in this
group, I should know better.)

> The only real question is, do they document it as an extension?

Yes, they do.
--
  | GurgleKat (Pete Gontier), pete@cavevax.ucsb.edu
  | .UUCP reply addresses bounce; try another path.
  | ...if you'd gone to Dartmouth, you'd not have had to take the math.