I'm wondering if Perl6's new regex can be applied to non-string things. I
seem to recall A5 mentioning something about strings tied to array
implementations; but I'm wanting something a little more powerful.
A bit of context: I use Perl for verification of big complex ASICs. We run a
simulation a
>> Having the subscript operator change the topic is, IMHO, a rather strong
>> violation of the principle of least surprise.
>
> I'm inclined to agree. I think I'd much rather not have it change there,
> since I'll frequently do stuff like this:
>
> my %hash;
> for qw(one two three) {
> %ha
Miko O'Sullivan aksed:
> what would "true" (the string) be converted to?
In a numeric context: 0 (as in Perl 5).
> Here's my point more
> explicitly: in a boolean context, there's no need to get any specific string
> (0, 1, "yup") as long as it correctly expresses true or false. It's whe
On Thu, Aug 01, 2002 at 06:17:11PM -0400, Uri Guttman wrote:
> do these instead:
>
> $bool += 0 ;
> ($x == $y) + 0
or even
$x == $y || 0
--
Never do today what you can put off till tomorrow.
On Thursday, August 1, 2002, at 04:05 PM, Mark J. Reed wrote:
> Having the subscript operator change the topic is, IMHO, a rather strong
> violation of the principle of least surprise.
I'm inclined to agree. I think I'd much rather not have it change there,
since I'll frequently do stuff like
On Fri, Aug 02, 2002 at 08:30:05AM +1000, Damian Conway wrote:
> @arr[@arr.length] = $var;
>
> or maybe just :
>
> @arr[.length] = $var;
>
> (if an array were to be made the topic inside its own accessor brackets).
I know this idea was just thrown in there, but I find that I really
From: "Dave Mitchell" <[EMAIL PROTECTED]>
> But perl5 already does this:
Dave gets the "First to Point Out the Feature Exists" award. I knew that
out of three ideas I'd be lucky if just one of them was actually a new
feature idea.
I might still say that the parens don't make things quite obvio
On Thu, Aug 01, 2002 at 06:02:14PM -0400, Miko O'Sullivan wrote:
> This is a small collection of ideas for the Perl6 language. Think of this
> posting as a light and refreshing summer fruit salad, composed of three
> ideas to while away the time during this August lull in perl6-language.
>
>
>
Miko O'Sullivan suggested:
> Give split an option to keep the delimiters in the returned array
As Dave mentioned, this already happens if you capture within the
split pattern.
>
> Set preferred boolean string for scope
It's possible t
> "MO" == Miko O'Sullivan <[EMAIL PROTECTED]> writes:
MO> Give split an option to keep the delimiters in the returned array
perl5 can already do that. just wrap the delim part in parens and split
will return them. also by using a lookahead/behind as the regex split
won't strip out that tex
On Thu, Aug 01, 2002 at 06:02:14PM -0400, Miko O'Sullivan wrote:
> It would be really groovy if that expression could be split with the
> delimiters in place, something like this:
>
>@tokens = split _/[?=*-+]/, $sql, keep=>'all';
>
> and get back an array with these values: ('rank', '=', '?'
This is a small collection of ideas for the Perl6 language. Think of this
posting as a light and refreshing summer fruit salad, composed of three
ideas to while away the time during this August lull in perl6-language.
Give split an option
pdcawley <[EMAIL PROTECTED]> writes:
> Bugger, I used L and pod2text broke it.
> http:[EMAIL PROTECTED]/msg10797.html
perlpodspec sez you can't use L<...|...> with a URL, and I'm guessing that
I just didn't look at that case when writing the parsing code in pod2text
because of that.
--
Russ Al
On 1 Aug 2002 [EMAIL PROTECTED] wrote:
> The mailing list archives are still not searchable (tell me about it),
> but Brent Dax points out that the ever wonderful Google has the "site:"
> keyword to do search restriction. I foresee a handy little autobookmark
> appearing on my gal
14 matches
Mail list logo
