On Tue, 01 Aug 2000, J. David Blackstone wrote:
> How about this: perhaps we should compile a list of system calls
> that _should_ remain in the core language. I think it will probably
> be very small.
I would suspect no more than the ones that perl needs internally for
itself, excluding, of course, self-definition.
Perl, internally, will need some form of I/O handling. Therefore, since
it's already going in anyway, that same I/O should also be available
to script space. Less code to break or fix. In theory. I suppose you
could put it in a module and reference back into the perl core.
Would that be too evil?
Shared memory, to pick one, probably won't be needed inside perl proper,
and can be unloaded to a external module.
Some of the variables should probably stay, just for completeness's
sake, in the core, whether Perl needs them or not.
($EUID and $EGID come to mind. $EUID is used, but I'm not sure about
$EGID. Either way, they probably shouldn't be separated.)
I would like to see some way of replacing or overriding what Perl core
provides with something external, so if some foolhardy^H^H^H^Hbrave
scripter wanted to replace standard Perl I/O with, say, O/I, they could.
I suppose whatever ends up as 'Perl 5 mode' would auto-include the
modules the former core functions disappeared into.
--
Bryan C. Warnock
([EMAIL PROTECTED])
