On Fri, Aug 18, 2000 at 08:46:17PM +0100, Richard Proctor wrote:
>
>There is one significant area of perl that has very little attention here
>(other than one of my RFCs) that is regexs.
Are you volunteering to chair a sublist?
*grin*
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://neti
Uri Guttman <[EMAIL PROTECTED]> writes:
> > "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
>
> PS> At 08:50 PM 8/19/00 -0400, [EMAIL PROTECTED] wrote:
> >> I do believe thbis is one of the reasons sysread is there
> >>
> >> perldoc -f sysread
>
> PS> Au contraire; sysread reads
On Sat, Aug 19, 2000 at 05:45:39PM -0700, Peter Scott wrote:
>At first I thought this was a -io item, but then I realized the -io part is
>easy; it's the -language part I need to get right :-)
Um. The -io sublist is called -language-io for a reason -- it's for
language discussions related to IO.
I think all discussion fo RFC 76 (reduce) should be on the new -data
sublist. Jeremy, am I on track here?
K.
--
Kirrily Robert -- <[EMAIL PROTECTED]> -- http://netizen.com.au/
Open Source development, consulting and solutions
Level 10, 500 Collins St, Melbourne VIC 3000
Phone: +61 3 9614 0949
On Fri, Aug 18, 2000 at 05:22:17PM -0500, David L. Nicol wrote:
>RFC: Perl6 is Final. There will Be No Perl7
>RFC: Everything is Accessible and Mutable
>RFC: The perl6 reference implementation, no matter how slow it is,
>will be written in perl5, in some kind of well defined virtual machine.
>
> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
PS> No, the point is not that I want truncated lines but that I want to say
PS> "toss/leave back the excess over 100,000 characters when I do a ,
PS> for I am sure that a line longer than that would be an error of some
PS> kind."
In reply to your message from the not too distant future: next Saturday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Sat, 19 Aug 2000 20:59:26 -0400
From: Jerrad Pierce
>Au
In reply to your message from the not too distant future: next Saturday AD
Reply-to: [EMAIL PROTECTED]
Return-receipt-to: [EMAIL PROTECTED]
Organization: a) Discordia b) none c) what's that?
Content-Typo: gibberish, charset=ascii-art
Date: Sat, 19 Aug 2000 20:50:44 -0400
From: Jerrad Pierce
I do
At 08:59 PM 8/19/00 -0400, [EMAIL PROTECTED] wrote:
> >Au contraire; sysread reads exactly the number of characters requested;
> >what I want is a way for programs that do all over the place to be
> >protected if someone throws a gargantuan number of characters at FH without
> >a newline. The $/
> "PS" == Peter Scott <[EMAIL PROTECTED]> writes:
PS> At 08:50 PM 8/19/00 -0400, [EMAIL PROTECTED] wrote:
>> I do believe thbis is one of the reasons sysread is there
>>
>> perldoc -f sysread
PS> Au contraire; sysread reads exactly the number of characters
PS> requested; what I
At 08:50 PM 8/19/00 -0400, [EMAIL PROTECTED] wrote:
>I do believe thbis is one of the reasons sysread is there
>
>perldoc -f sysread
Au contraire; sysread reads exactly the number of characters requested;
what I want is a way for programs that do all over the place to be
protected if someone t
At first I thought this was a -io item, but then I realized the -io part is
easy; it's the -language part I need to get right :-)
I have often thought that there should be a way to say that a readline()
should limit the length of line it could return, or in circumstances where
the input source
On Fri, Aug 18, 2000 at 03:15:54PM -0700, Steve Fink wrote:
> There would still be a use of a /f like flag, though -- treat all (...)
> like (?:...). That would make the regex more likely to be DFA-able, and
> is often what I want but I don't want to clutter up my regex with those
> nasty ?:'s eve
> I think this does the right thing too:
>
> @out = sort ^0 cmp ^a, @in;
>
> Since numbered placeholders have higher priority than named, it
> should create the function
>
> sub ($, $a) { $_[0] cmp $_[1] }
> When the curry is evaluated, the a: parameter is bound t
> > /\A(?s:(?!and).)*\Z/
> >
> > /pattern returned from ${\some_function} as part of a regex/
> >
> > /match any of (${\join'|',@list}) here/
>
> I am not saying these things can't be done, in fact I was saying they can
> but was rather asking what should be made easier?
Damian Conway wrote:
> sub sort (^&comparator, @list) {
> for (1..@list**3) {
> my ($i, $j) = (rand(@list), rand(@list));
> @list[$i,$j] = @list[$j,$i]
> unless $comparator->(a: $list[$i], b: $list[$j]);
>
Dave Storrs wrote:
> On Thu, 17 Aug 2000, Jonathan Scott Duff wrote:
> > BTW, if we define C to map keys of a hash to named place holders
> > in a curried expression, this might be a good thing:
> >
> > with %person {
> > print "Howdy, ", ^firstname, " ", ^lastname;
> > }
> >
On Fri 18 Aug, Damian Conway wrote:
>> All of these can be done today but are not necessarily "easy".
>>
>
> /\A(?s:(?!and).)*\Z/
>
> /pattern returned from ${\some_function} as part of a regex/
>
> /match any of (${\join'|',@list}) here/
>
I am not saying these things can't be done,
> > Now, go home and write it out 100 times:
> >
> > "Array and placeholder indices both start at *zero*!"
> Array and placeholder indices both start at *zero*!
> Array and placeholder indices both start at *zero*!
> Array and placeholder indices both start at *zero*!
> Array
Damian Conway wrote:
>> Well, RFC 23 doesn't mention ^0, and has several examples starting
>> at ^1. And it draws the analogy between ^1, ^2, etc and $1, $2,
>> etc. I didn't make it up.
>
> My apologies. The examples you refer to are incorrect. They were added by
> a helper, but the
Array and placeholder indices both start at *zero*!
Array and placeholder indices both start at *zero*!
Array and placeholder indices both start at *zero*!
Array and placeholder indices both start at *zero*!
- Original Message -
From: "Damian Conway" <[EMAIL PROTECTED]>
To: "Jarkko Hietani
21 matches
Mail list logo
