NotFound wrote:
By the way, as mentioned in other thread there is a problem with plain
%s in parrot printf-alike functions. It does not handle well a NULL c
string. This must be fixed. And before, given the current
implementation, the behavior of string_make and his successor in the
strings pdd,
>> We have more: PIO_printf, PIO_eprintf, Parrot_printf, Parrot_eprintf
>> and Parrot_fprintf. The Parrot_ ones are a wrapper around the PIO_s,
>> with added check for extern usage, and that does not need #include io
>> files.
>
> Yes, to be more accurate, we have a whole range of PIO functions. Bu
NotFound wrote:
On Wed, Sep 10, 2008 at 9:21 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
chromatic wrote:
That C string leaks. We should have a diagnostic printf which supports
the %Ss format we use in exception formatting strings.
We have one, it's called PIO_fprintf. But, it's only used o
On Wed, Sep 10, 2008 at 9:21 AM, Allison Randal <[EMAIL PROTECTED]> wrote:
> chromatic wrote:
>>
>> That C string leaks. We should have a diagnostic printf which supports
>> the %Ss format we use in exception formatting strings.
>
> We have one, it's called PIO_fprintf. But, it's only used once in
chromatic wrote:
That C string leaks. We should have a diagnostic printf which supports
the %Ss format we use in exception formatting strings.
We have one, it's called PIO_fprintf. But, it's only used once in the
repository, in an STM macro.
Added to the I/O milestone tasklist.
Allison
On Tuesday 09 September 2008 15:34:21 [EMAIL PROTECTED] wrote:
> [pdd27mmd] Fix failing coding standards test for line length.
>
>
> Modified: branches/pdd27mmd/src/multidispatch.c
> ===
>=== --- branches/pdd27mmd/src/multidis
