At 08:51 AM 3/29/00 -0500, Charles Lane wrote:
>Dan Sugalski [EMAIL PROTECTED]
>
> > At 12:25 PM 3/28/00 -0500, Charles Lane wrote:
> > >You set $ENV{PERL_MBX_SIZE} if you want something different.
>
> > I think I'd like something a little more private, which is why I was
> > thinking of a magic variable. %ENV settings affect the environment and
> > propagate around--that's OK in some cases, but a little unsubtle.
>
>Well, one of the main reasons for making the MBX size smaller is to
>avoid exhausting your buffered I/O byte count quota. The quota is
>"pooled" for use by all processes in a single job so it makes sense to
>propagate MBX size restrictions to child processes, so that the parent
>has some say over how much resources the kids are using.
What, everyone doesn't have a bytlm of 10M? Huh. :)
>Seemed like a logical was the, um, logical way to do that.
The logical's a great way to default things, no doubt. But setting $ENV for
a single subprocess spawn seems a bit heavy-handed, especially if you want
it for the spawn but not for the subprocess itself. local() works if you
don't mind it propagating down. (I just ended up figuring how perl manages
local and scopes and stuff for completely different reasons. Cool and
mildly twisted. I like!)
Not a huge deal, though we need to document it better. (Well, document it
at all) The VMS docs need a complete overhaul and major porking out anyway.
I'll see what I can get time to work on.
Dan
----------------------------------------------------------------------------
Dan Sugalski General and VMS-specific perl training
[EMAIL PROTECTED]
Mail me for more details
