At 02:22 PM 8/26/00 +0200, H.Merijn Brand wrote:
> > It seems that it ought to be possible to evaluate something in a list
> > context and test whether there are any entries in the resulting list
> > without having to reevaluate the expression in a scalar context. The
> > work-around with the tri
> Perl should become PEARL
This is a joke, right? :-)
Perl already *was* PEARL. Way back when. Larry changed it *to* Perl
because there was already a different PEARL.
> Even many books display PEARL as the Logo for the PERL
> language book.
Maybe they're really talking about PEARL. If not, I w
At 06:59 AM 8/26/00 -0600, Tom Christiansen wrote:
>[I know this is not your quote, but your quotee's quote]
>
> >> There is obviously no need to modify the behavior of the C<&&> operator.
>
>Is one wholly certain of this?
>
> DB<1> @c = (1..3)
> DB<2> @a = @b && @c
> DB<3> x @a
Bart Lateur writes:
: Apropos those extended mechanisms: couldn't we use the same mechanism as
: is currently in use for $!, for $@ too? I mean: $! in numerical context
: gives an error number, in string context a text string. Then
:
: die "I'm outta here: $!";
:
: should assign both the n
Tom Christiansen writes:
: It would appear that altering &&/|| on LHS context would entail,
: in the list assignment scenario, calling that operand in list context
: and then deciding whether it were true or not by some "intuitive"
: means (almost certainly by using whether its element count were
Suresh Kumar R writes:
: Perl should become PEARL
Er, the folks at http://www.irt.uni-hannover.de/pearl/pearl-gb.html
might have something to say about that.
Larry
Bart Lateur wrote:
> I *like* the =~ syntax,
ich auch.
> and I would hope we could extend it
> to more functions that change one of their parameters, like
> sysread/read:
>
> $bytes_read = $string =~ sysread FILE, $bytes_to_read;
RFC139 would enable precisely that capability.
--
John
[I know this is not your quote, but your quotee's quote]
>> There is obviously no need to modify the behavior of the C<&&> operator.
Is one wholly certain of this?
DB<1> @c = (1..3)
DB<2> @a = @b && @c
DB<3> x @a
0 0
DB<4> x @b
empty array
It's hard to argue
Reply on laptop in wilderness (no network) holydays me void this message by
other messages sent in my absence. Ignore if so.
On Thu, 17 Aug 2000 08:28:50 -0400 (EDT), Philip Newton
<[EMAIL PROTECTED]> wrote:
> On Tue, 15 Aug 2000, Michael Fowler wrote:
>
> > So what's insufficient about:
> >
>
Reply on laptop in wilderness (no network) holydays me void this message by
other messages sent in my absence. Ignore if so.
On 5 Aug 2000 21:40:43 -, Perl6 RFC Librarian <[EMAIL PROTECTED]> wrote:
> This and other RFCs are available on the web at
> http://dev.perl.org/rfc/
>
> =head1 TITL
Sumesh,
Please read http://dev.perl.org/ for the correct way to post a Perl 6
RFC. The first thing you need to know is that they should go to
[EMAIL PROTECTED], not direct to the mailing list.
Secondly, you need to make sure that things your'e RFCing aren't already
available in Perl. Some of t
Righto. I'll coach Sumesh through how to post an RFC properly, and how
to check whether something's in Perl yet or not.
DO NOT fill -language with discussions of these pseudo-RFCs. Please.
I'm begging you.
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source dev
=head1 TITLE
Subscript should be known for a multidimesional array
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
When we use $ARGV[$#ARGV] it gives the Subscript of the last elemen
=head1 TITLE
In built SGML/XML parser required
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
There is no true inbuilt parser in PERL, it has to be built.
=head1 DESCRIPTION
Publi
head1 TITLE
onerror() builtin function required
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
Perl should handle all the errors and sigtraps with one
onerror builtin funciton
=hea
=head1 TITLE
Perl should become PEARL
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
Perl should become PEARL which indicates the true meaning for
this language
=head1 DESCRIPTION
=head1 TITLE
Builtin function to insert an element in the middle of the array (including
multidimensional)
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
A builtin function should b
=head1 TITLE
Subscript should be known for a multidimesional array
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
When we use $ARGV[$#ARGV] it gives the Subscript of the last elemen
=head1 TITLE
Time should be displayed depending upon the parameter
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
A builtin function should which returns appropriate time according
=head1 TITLE
Global time should be made available
=head1 VERSION
Maintainer: Suresh Kumar .R <[EMAIL PROTECTED]>
Date: 2000-08-26
Version: 1
Mailing List: [EMAIL PROTECTED]
Number: ?
=head1 ABSTRACT
A builtin function should which returns appropriate time according
to the that count
On Fri, 25 Aug 2000 20:44:32 -0400, John Porter wrote:
>Nathan Wiger wrote:
>>
>> I do think
>> it's worth considering if we're dead-set on losing =~.
>
>But are we?
I hope not. I *like* the =~ syntax, and I would hope we could extend it
to more functions that change one of their parameters, l
21 matches
Mail list logo
