David L. Nicol writes:
: I am going to miss doublequoting being the default quoting for
: here strings. I find that to be a very nice optimization and
: would like to know more about the reasoning behind taking it
: away. I worry that official standard p6 will be more difficult
: to use than off
On Thu, May 03, 2001 at 10:14:47PM -0500, David L. Nicol wrote:
>
> I am going to miss doublequoting being the default quoting for
> here strings. I find that to be a very nice optimization and
> would like to know more about the reasoning behind taking it
> away. I worry that official standard
I am going to miss doublequoting being the default quoting for
here strings. I find that to be a very nice optimization and
would like to know more about the reasoning behind taking it
away. I worry that official standard p6 will be more difficult
to use than official standard p5.
--
> > It also reminds me of mjd's mention of: my($first) = sort {...} @list;
> > being O(n) if Perl were really Lazy.
>
> But it would need a completely different algorithm. Which is not too
> bad. And even
>
> my ($first, $second, $third) = sort {...} @list;
>
> is kind-of plausible. So
Dave Storrs said:
> On 3 May 2001, Ilya Martynov wrote:
> > >> You can serialize/deserilize object with Storable
> > >>
> > >> $foo = new Bar
> > >> store_fd $foo, \*SOCKET;
> > >>
> > >> and on the other end
> > >>
> > >> $foo = retrieve_fd \*SOCKET;
> > >> $foo->bar;
> > >>
> > >> It will work i
Larry's Second Apocalypse (that's part 2 of his travels through the
Camel writing about what will change in perl 6) is on the web at:
http://www.perl.com/
Enjoy!
Nat
> The biggest problem I have with sandboxing is that to do it right is
> apparently difficult, judging by the number of people that get it wrong. We
> need to rope in a security expert, I think, for the design.
>
> I don't suppose we have one in the house somewhere?
"Where have you gone, Malco
From: Dan Sugalski [mailto:[EMAIL PROTECTED]]
>
> At 05:22 PM 5/3/2001 -0400, John Porter wrote:
> >David L. Nicol wrote:
> > > is sandboxing something a language should support
> > > at all, or is it best left to the OS to provide
> > > a solid chroot facility?
> >
> >IMHO this is one of those t
At 05:22 PM 5/3/2001 -0400, John Porter wrote:
>David L. Nicol wrote:
> > is sandboxing something a language
> > should support at all, or is it best left to the OS to provide
> > a solid chroot facility?
>
>IMHO this is one of those things that should be kept firmly
>in the front of our minds as
David L. Nicol wrote:
> In all the discussion of customizing the parser, let us not
> forget that we also need to be able to limit the parser.
O.k., but what you say below isn't about limiting the parser,
it's about limiting the VM.
> is sandboxing something a language
> should support at all,
On 3 May 2001, Ilya Martynov wrote:
> >> You can serialize/deserilize object with Storable
> >>
> >> $foo = new Bar
> >> store_fd $foo, \*SOCKET;
> >>
> >> and on the other end
> >>
> >> $foo = retrieve_fd \*SOCKET;
> >> $foo->bar;
> >>
> >> It will work if you have Bar module on both ends.
In all the discussion of customizing the parser, let us not
forget that we also need to be able to limit the parser. The
"Penguin" module offers one interface for doing that. But
the larger question remains, is sandboxing something a language
should support at all, or is it best left to the O
On Wed, 2 May 2001, Dan Brian wrote:
> Another snippet from the .NET whitepaper:
>
>
> Everyone believes the Web will evolve, but for that evolution to be
> truly empowering for developers, businesses, and consumers, a radical new
> vision is needed. Microsoft's goal is to provide that vision
At 03:11 PM 5/2/2001 -0700, Dave Storrs wrote:
>On Tue, 1 May 2001, Dan Sugalski wrote:
>
> > Right. What I'm thinking would be a good place to get to is a list of the
> > functionality that the debugger needs to provide or have available to it
> > from the interpreter, rather than the actual in
Larry Wall wrote:
[...]
> Then Perl language variants could go the other way and be:
>
> PermMicro Perl
> PernNano Perl
> PeroJava Perl
> PerpPython Perl
> PerqQuick Perl
> PerrRuby Perl
> PersStrict Perl
> Pe
On Thu, May 03, 2001 at 12:32:40PM -0700, Larry Wall wrote:
: Edward Peschko writes:
: : > : (is a nice city in Italy with a great symbol, the tower of Pisa).
: : > :
: : > : a'P' at the beginning, which means 'Perl',
: : > : an 'I' which may mean 'Interpreter',
: : > : a
Edward Peschko writes:
: > : (is a nice city in Italy with a great symbol, the tower of Pisa).
: > :
: > : a'P' at the beginning, which means 'Perl',
: > : an 'I' which may mean 'Interpreter',
: > : a'S' which may means'Six'
: > : an 'A' which may
From: "Alexander Farber (EED)" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 02, 2001 5:13 AM
Subject: Please make "last" work in "grep"
> Here I am looking for a button with a special name - "Delete ..." -
> and there can be only one such button, so I have to interrupt the
>
> : (is a nice city in Italy with a great symbol, the tower of Pisa).
> :
> : a'P' at the beginning, which means 'Perl',
> : an 'I' which may mean 'Interpreter',
> : a'S' which may means'Six'
> : an 'A' which may means'Alpha'
>
> I
Hey, all.
This whole discussion on using . instead of -> made me think a lot about
the Perl 6 language. Actually, this was the more recent of many
religious wars happening on perl6-language about choosing this or that
way of doing something. I remember many others like using my or using
dynamic
>> You can serialize/deserilize object with Storable
>>
>> $foo = new Bar
>> store_fd $foo, \*SOCKET;
>>
>> and on the other end
>>
>> $foo = retrieve_fd \*SOCKET;
>> $foo->bar;
>>
>> It will work if you have Bar module on both ends.
DS> Right, but I want it to work if you don't...
Then mayb
On Wed, May 02, 2001 at 04:26:27PM -0500, Jarkko Hietaniemi wrote:
> You are saying that the Clippy wasn't originally and truly annoying? :-)
Annoying enough to spawn vigor!
http://www.red-bean.com/~joelh/vigor/
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl
Michael G Schwern <[EMAIL PROTECTED]> writes:
> On Wed, May 02, 2001 at 08:05:29AM -0700, Larry Wall wrote:
> > Michael G Schwern writes:
> > : (grep {...} @stuff)[0] will work, but its inelegant.
> >
> > It's inelegant only because the slice doesn't know how to tell the
> > iterator it only nee
23 matches
Mail list logo
