Re: PERL_SYS_INIT()

On 2011-10-31, Hallvard B Furuseth <h.b.furuseth@xxxxxxxxxxx> wrote:
AFAICT they are only different on OS/2, but _INIT3 was introduced in
5.6, so you should probably use it anyway. (They probably *ought* to be
different at least on Win32, as well, since the Win32 init code affects
the environment, but currently they aren't.)

Sounds like it's safest to use INIT when available and INIT3 otherwise,
then. That leaves as much as possible of the work to Perl.

The opposite. INIT is not supported. If it works, then only
accidentally.

env MUST be passed as the third argument to INIT3 (although it might
be coded to do something reasonable when the third argument is NULL -
do not have the source with me now to check.

Hope this helps,
Ilya
.

Relevant Pages

  • Re: PERL_SYS_INIT()
    ... different at least on Win32, as well, since the Win32 init code affects ... Sounds like it's safest to use INIT when available and INIT3 otherwise, ... That leaves as much as possible of the work to Perl. ...
    (comp.lang.perl.misc)
  • Restarting X
    ... What is the cleanest way to restart X? ... In RH 7.3 I can just to init3, ... a second, and do init 5. ... Is there an equivalent method with Debian? ...
    (Debian-User)
  • Re: PERL_SYS_INIT()
    ... AFAICT they are only different on OS/2, ... Sounds like it's safest to use INIT when available and INIT3 otherwise, ... That leaves as much as possible of the work to Perl. ...
    (comp.lang.perl.misc)
  • Re: [SLE] Re: Need help with unreadable font in 9.1!!!
    ... > well, perhaps XF86Config is hosed, ... > init 3 ... How do I get into init3 from a command line? ...
    (SuSE)