Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> They should not fail more drastic than necessary. Only fail if its not
> possible to report an error to the upper level.
Yep. That's right. To panic() is not necessary nost of the time.
> bye
> boe
leo
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Juergen Boemmels wrote:
>
> > Leopold Toetsch <[EMAIL PROTECTED]> writes:
> > [...]
>
> >
>
> >>PIO_eprintf
> >>PIO_printf
> >>
> >>for printing to stderr/stdout during 1st interpreter construction &
> >>destruction if something goes wrong. In all o
Juergen Boemmels wrote:
Leopold Toetsch <[EMAIL PROTECTED]> writes:
[...]
PIO_eprintf
PIO_printf
for printing to stderr/stdout during 1st interpreter construction &
destruction if something goes wrong. In all other cases we have an
valid interpreter (or an parent interpreter if any).
This means
Leopold Toetsch <[EMAIL PROTECTED]> writes:
[...]
> PIO_eprintf
> PIO_printf
>
> for printing to stderr/stdout during 1st interpreter construction &
> destruction if something goes wrong. In all other cases we have an
> valid interpreter (or an parent interpreter if any).
This means all the Par
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> Hello,
> Some Parrot functions allow a NULL interpreter and some
> don't. Parrot_warn for example fails badly if called with a
> NULL-interpreter, but in config/gen/platform/ansi.c in
> Parrot_floatval_time it is exactly called in this way.
> So what
Hello,
Some Parrot functions allow a NULL interpreter and some
don't. Parrot_warn for example fails badly if called with a
NULL-interpreter, but in config/gen/platform/ansi.c in
Parrot_floatval_time it is exactly called in this way.
So what functions should allow for a NULL interpreter, which sho
