Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re: [LONG] Possible utf8 implementation #607

p5pRT opened this issue Sep 20, 1999 · 2 comments

Re: [LONG] Possible utf8 implementation #607

p5pRT opened this issue Sep 20, 1999 · 2 comments


Copy link

p5pRT commented Sep 20, 1999

Migrated from (status was 'resolved')

Searchable as RT1467$

Copy link

p5pRT commented Sep 20, 1999

From The RT System itself

  Nick> of Perl_croak("Oops %s ...",charptr)

Do you mean inside the core or from XS?
  Nick> - can we have (say) %ls to say string is utf8 - is this too
  Nick> weird or already "taken" for wchar_t ? - always use %_ -
  Nick> another nifty idea from the list?

You may recall we discussed enhancing Perl_croak to throw objects in
the developer session at TPC3.0. Graham, Andy Wardley & myself
volunteered to investigate this with a view to providing Perl with a
complete, light-weight exceptions mechanism based on Graham's Error &
Fatal modules & what ever we thought appropriate to rip-off from other
languages, notably Java's exception/error class hierarchy. My vote
goes for insisting on Perl_croak being 7bit clean for now, till we
have a clearer picture of what throwing objects from the core means.

  Nick> $@​ is an SV so there is no issue with its holding the value,
  Nick> what is less clear is Perl_warner() & other spots where
  Nick> Perl_mess() is playing with strings.

These should stop doing that anyway.

"If 8-year-old boys discharging loaded firearms into their own legs
isn't necessary to the maintenance of a well-regulated militia, I
don't know what is." - Randal Cummings as reported in The Onion, 25/5/99

Copy link

p5pRT commented Apr 22, 2003

@iabyn - Status changed from 'stalled' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

1 participant