This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Pascal Strings -- WITHDRAWN
- To: Ziemowit Laski <zlaski at apple dot com>
- Subject: Re: PATCH: Pascal Strings -- WITHDRAWN
- From: Tom Tromey <tromey at redhat dot com>
- Date: 05 Jul 2001 19:13:09 -0600
- Cc: gcc-patches at gcc dot gnu dot org
- References: <200107052349.f65NnNw28852@scv2.apple.com>
- Reply-To: tromey at redhat dot com
>>>>> "Zem" == Ziemowit Laski <zlaski@apple.com> writes:
Zem> Actually, now I realize that 255 as the length limit was right in
Zem> the first place. Aside from avoiding the overflow problem
Zem> described here, 255 ensures \ that Pascal strings are
Zem> *portable*. Correct me if I'm wrong, but one wouldn't want to
Zem> have 1000-char Pascal strings that compile fine on one platform
Zem> but not on others.
I've been reading this thread. Why is having this be
target-independent desirable? Is there an actual use for \p strings
on the C4X (or whatever the non-8-bit-char architecture is called).
Wouldn't it be just as reasonable to document the limit as 255
characters? We could always extend it if/when it becomes relevant.
Tom