Hi,
>> This code:
>>
>> my $a='A';
>> $a ~~ s:perl5:g/A/{chr(65535)}/;
>> say $a.bytes;
>>
>> Outputs "0". Why?
>
>
> \u is not a legal unicode codepoint. chr(65535) should raise an
exception of some type. So the above code does seem show a possible
bug. But as that chr(65535) is an undefin
Nick Glencross <[EMAIL PROTECTED]> wrote:
> This patch fixes a problem which can occur in this example:
> .sub test
> .const float a = 12
> print a
> print_newline
> .end
Ah yep.
>
> +if (t != 'P' && t != val->set)
> +IMCC_fataly(interp, E_TypeError,
> +
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #34994]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34994 >
A Python example first:
$ python
>>> import sys
>>> print sys.maxint
2147483647
Hi,
Yes, the value 0x can be stored as either 3 byte UTF-8 string or a 2
byte UCS-2 value, but the Unicode standard specifically says that the
values 0x, 0xFFFE and 0xFEFF are NOT valid codepoints and should
never appear in a Unicode string. 0x is reserved for out-of-band
signaling
hi,folks.
I am reading PMC C source code and reading some document("
http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Some questions:
*this PMC design have changed?
*any body offer some advice that learn PMC C source code and PMC's theory?
Thanks.
/\ /\
/ |
# New Ticket Created by Nick Glencross
# Please include the string: [perl #34991]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34991 >
Here's another odd one, which looks const-related. Uncommenting the '+='
line causes
On Thu, 31 Mar 2005 21:17:39 -0500, [EMAIL PROTECTED] (MrJoltCola)
wrote:
> At 05:57 PM 3/31/2005, Nigel Sandever wrote:
> >Is Parrot bytecode reentrant?
>
> Yes.
>
> >That is, if I want to have two instances of a class in each of two
> >threads, will
> >the bytecode for the class need to be lo
Thank you, applied!
jens
hi,folks.
I am reading PMC C source code and reading some document("
http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Some questions:
*this PMC design have changed?
*any body offer some advice that learn PMC C source code and PMC's theory?
Thanks.
/*
p2p is a protocol or a compiler?
*/
Hi,
my $a='A';
$a ~~ s:perl5:g/A/{chr(65535)}/;
say $a.bytes;
Outputs "0". Why?
\u is not a legal unicode codepoint. chr(65535) should raise an
exception of some type. So the above code does seem show a possible
bug. But as that chr(65535) is an undefined char, who knows what the
code is a
BÁRTHÁZI András wrote:
Hi,
This code:
my $a='A';
$a ~~ s:perl5:g/A/{chr(65535)}/;
say $a.bytes;
Outputs "0". Why?
Bye,
Andras
\u is not a legal unicode codepoint. chr(65535) should raise an
exception of some type. So the above code does seem show a possible
bug. But as that chr(65535) is
BÁRTHÁZI András wrote:
Hi,
>> This code:
>>
>> my $a='A';
>> $a ~~ s:perl5:g/A/{chr(65535)}/;
>> say $a.bytes;
>>
>> Outputs "0". Why?
>
>
> \u is not a legal unicode codepoint. chr(65535) should raise an
exception of some type. So the above code does seem show a possible
bug. But
John Williams wrote:
Good point. Another one is: how does the meta_operator determine the
"identity value" for user-defined operators?
Does it have to? The definition of the identity value---BTW, I like
the term "neutral value" better because identity also is a relation
between two values---is tha
Hi,
There will be a Parrot/PUGS Hack-a-thon at the Austrian Perl Workshop, which
takes place on 9th and 10th June in Vienna, Austria.
Autrijus Tang, Chip Salzenberg and Leo Toetsch will be there. You should be
there too :-)
I'll be there, too. ;)
Bye,
Andras
Someone's pointed this thread out to me, so I'm going to shove an oar in
following a few posts. I've done a fair bit of security work, so feel
free to ask me to explain, justify or provide references for anything.
On Wed, 2005-04-13 at 17:01 -0400, Dan Sugalski wrote:
> All security is done on a p
On Wed, 2005-04-13 at 17:51 -0400, Aaron Sherman wrote:
> On Wed, 2005-04-13 at 17:01, Dan Sugalski wrote:
> > So here's what I was thinking of for Parrot's security and quota
> > model. (Note that none of this is actually *implemented* yet...)
> [...]
> > It's actually pretty straightforward, the
Steven Philip Schubiger wrote:
[ cc'ed list, so that folks know about takers ]
On 15 Apr, Leopold Toetsch wrote:
: 5) along with bringing the config online, some cleanup and renaming
: wouldn't harm e.g. "iv" vs "opcode_t", "intvalsize" vs "intsize" vs
: "opcode_t_size" ...
This part seems appea
Cory Spencer <[EMAIL PROTECTED]> wrote:
> I'd like to announce the creation of the Parrot Common Lisp project, which
> aims to implement a significant subset of the Common Lisp language.
Wow. I can even do something with it:
$ ../parrot lisp.imc
-> (+ 2 5)
7
-> (list 1 2 3)
(1 . (2 . (3 . NIL)))
Continuing the MMD infix plan, we now have:
1) the subtract MMD functions are converted to the new function signature:
PMC* subtract(PMC* value, PMC* dest)
If C isn't NULL it's set to the result of the operation and the
result is returned. This is the existing behavior. The TODO new "n_sub"
opc
On Thu, 2005-04-14 at 09:51 -0700, Dave Whipp wrote:
> Dan Sugalski wrote:
>
> > All security is done on a per-interpreter basis. (really on a per-thread
> > basis, but since we're one-thread per interpreter it's essentially the
> > same thing)
> ...
> >* Number of open files
> >* IO ope
On Wed, 2005-04-13 at 22:03 -0400, Michael Walter wrote:
> Dan,
>
> On 4/13/05, Dan Sugalski <[EMAIL PROTECTED]> wrote:
> > All security is done on a per-interpreter basis. (really on a
> > per-thread basis, but since we're one-thread per interpreter it's
> > essentially the same thing)
> Just to
Nigel Sandever <[EMAIL PROTECTED]> wrote:
> When a sub that closes over a variable
> my $closure = 0;
> sub do_something {
> return $closure++:
> }
> is called from two threads, do the threads share a single closure or
> each get their own separate closure?
AFAIK
On Thu, 2005-04-14 at 09:11 -0400, Dan Sugalski wrote:
> At 10:03 PM -0400 4/13/05, Michael Walter wrote:
> > > Each running thread has two sets of privileges -- the active
> >> privileges and the enableable privileges. Active privs are what's
> >> actually in force at the moment, and can be dr
I was doing some work on Parrot::Test today and was replacing this code
with something more cross platform.
# Run the command in a different directory
my $command = 'some command';
$command= "cd $dir && $command" if $dir;
system($command);
I replaced it with th
David Wheeler skribis 2005-04-14 21:32 (-0700):
> I was going to say that that was inconsistent, but since you never need
> to repeat a letter in a character class, well, I guess it isn't. But
> the first person to write <[a...]> gets what's comin' to 'em.
Given ASCII, <[\x20...]> would then be
Bloves Mr <[EMAIL PROTECTED]> wrote:
> hi,folks.
> I am reading PMC C source code and reading some document("
> http://www.perl.com/pub/a/2002/01/30/pmcs.html";).
Despite that the text is rather old, it's remarkably valid still.
> Some questions:
> *this PMC design have changed?
The internal la
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #34999]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=34999 >
Some outdated files:
lib/Parrot/PackFile/*
lib/Parrot/PackFile.pm
lib/Parr
On Thu, 2005-04-14 at 21:32 -0700, David Wheeler wrote:
> On Apr 14, 2005, at 7:06 PM, Patrick R. Michaud wrote:
>
> > So, <[a.z]> matches "a", ".", and "z",
> > while <[a..z]> matches characters "a" through "z" inclusive.
>
> I was going to say that that was inconsistent, but since you ne
* Adrian Howard <[EMAIL PROTECTED]> [2005-04-14T15:37:07]
> On 14 Apr 2005, at 11:36, Leon Brocard wrote:
> >Oh, I forgot to mention to perl-qa that I wrote Test::Expect:
> > http://search.cpan.org/dist/Test-Expect/
>
> It's nice. Already used it :-)
Does anyone who has used both Test::Expect an
"Mark A. Biggar" <[EMAIL PROTECTED]> wrote:
:BÁRTHÁZI András wrote:
:
:> Hi,
:>
:> This code:
:>
:> my $a='A';
:> $a ~~ s:perl5:g/A/{chr(65535)}/;
:> say $a.bytes;
:>
:> Outputs "0". Why?
:>
:> Bye,
:> Andras
:>
:
:\u is not a legal unicode codepoint. chr(65535) should raise an
:except
- Original Message -
From: "Aaron Sherman" <[EMAIL PROTECTED]>
To: "David Wheeler" <[EMAIL PROTECTED]>
Cc: "Perl6 Language List"
Sent: Friday, April 15, 2005 2:00 PM
Subject: Re: should we change [^a-z] to <-[a..z]> instead of <-[a-z]>?
> On Thu, 2005-04-14 at 21:32 -0700, David Wheeler
I'm not quite sure, but it seems that some of the MMD functions may
better be vtable methods:
- bitwise_sh[rl]*shift by anything other then int?
- bitwise_lsris missing generally
or even just a plain opcode only:
- logical_{or,and,xor} return a PMC depending on the boolean value
What
Am I the only one who thinks <[a-z]> is ugly and hard to type because of
the nested brackets? The same goes for <{...}>. The latter can't easily
be fixed, I think, but the former perhaps can. If there are more who
think it needs to, that is. And <{}> is a bit easier to type because all
four are shi
On Fri, Apr 15, 2005 at 02:58:44PM +0200, Juerd wrote:
> Am I the only one who thinks <[a-z]> is ugly and hard to type because of
> the nested brackets? The same goes for <{...}>. The latter can't easily
> be fixed, I think, but the former perhaps can.
Part of the thinking behind this is that the
>
> even sillier question:
> if <[a.z]> matches "a", "." and "z"
> and <[a...]> matches all characters from "a" including (for some
> definition of 'all')
>
> how will be range \x21 .. \x2e written?
> <[!..\.]>? (i.e. "." escaped?)
>
I was assuming from Larry's mail that <[a...]> would parse as
Aaron Sherman wrote in perl.perl6.language :
>
> A silly question: is there a canonical character set from which we
> extract these ranges? Are we hard-coding Unicode here, or is there some
> way for the user to specify the character set for ranges?
Perl 5 forces [a-z] (or [i-j] for that matter) t
On Fri, Apr 15, 2005 at 01:01:58PM -, Rafael Garcia-Suarez wrote:
> Aaron Sherman wrote in perl.perl6.language :
> >
> > A silly question: is there a canonical character set from which we
> > extract these ranges? Are we hard-coding Unicode here, or is there some
> > way for the user to specify
On 15 Apr, Leopold Toetsch wrote:
: That stuff is all in Perl code under the config dir, e.g:
:
: $ find config -type f | xargs grep -w intsize
This clarifies some of my unapproved assumptions, although src has
some files containing these keywords too.
: I think we should have:
:
:INTVAL_t
# New Ticket Created by FranÃois PERRAD
# Please include the string: [perl #35000]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/rt3/Ticket/Display.html?id=35000 >
small mistake in [perl #34986] :
with ICU 3.2, the library icudata.lib is renamed i
I've corrected a few spelling and punctuation errors;
since I'm not done yet, I'd like to know, whether I should
continue, or if the general consensus is, that it's mostly
needless nitpicking.
Punctuation has only been corrected, if punctuation was already
partly present; if totally absent, I di
MMD subroutines "add" are done.
* removed all mathematical functions from Tcl scalars - all is inherited now
I forgot to mention in MMD 23:
* If you have an overriden __add or __subtract function, either defined
as @MULTI or registered via mmdvtregister, these functions must now
return the destin
According to Cory Spencer:
> I'd like to announce the creation of the Parrot Common Lisp project
Excellent!
> * It's not a compiler yet, although I've got plans for that down the
> road.
(declare (type PerlString s)) ? :-)
--
Chip Salzenberg- a.k.a. -<[EMAIL PROTE
One more, and my fingers & brain are getting tired of these changes.
If someone wants to continue (and complete it during night here ;-),
it's a simple job:
1) vtable.tbl
- change existing signature of next infix operation
- add inplace variant directly below it
2) imcc/parser_util.c:is_inf
On Fri, Apr 15, 2005 at 03:11:59AM -0700, Michael G Schwern wrote:
: Error handling is simple, a failed chdir returns undef and sets errno.
:
: $CWD = $dir err die "Can't chdir to $dir: $!";
Offhand, I guess my main semantic problem with it is that if a chdir
fails, you aren't in an undefin
Among the various ways of declaring variables, will Perl 6 have a way to
say, "this variable is highly temporary, and may be re-declared within
the same scope, or in a nested scope without concern"? I often find
myself doing:
my $sql = q{...};
...do some DB stuff...
my $sql
On Fri, Apr 15, 2005 at 12:45:14PM +1200, Sam Vilain wrote:
: Larry Wall wrote:
: > Well, only if you stick to a standard dialect. As soon as you start
: > defining your own macros, it gets a little trickier.
:
: Interesting, I hadn't considered that.
:
: Having a quick browse through some of th
Aaron Sherman skribis 2005-04-15 11:45 (-0400):
> What I'd really like to say is:
> throwawaytmpvar $sql = q{...};
> throwawaytmpvar $sql = q{...};
I like the idea and propose "a", aliased "an" for this.
> It should probably be illegal to:
> throwawaytmpvar $sql = q{...};
>
On Fri, Apr 15, 2005 at 11:45:16AM -0400, Aaron Sherman wrote:
: Among the various ways of declaring variables, will Perl 6 have a way to
: say, "this variable is highly temporary, and may be re-declared within
: the same scope, or in a nested scope without concern"? I often find
: myself doing:
:
On Fri, Apr 15, 2005 at 06:04:32PM +0200, Juerd wrote:
: No, Ucfirst it can't be, I think. And ALLCAPS is ugly. @ is taken (and
: ugly). Suggestions?
Maybe we could define an "ok" operator that suppresses only the
*first* warning produced by its argument(s). Then if you get multiple
warnings, you
On Fri, Apr 15, 2005 at 09:17:13AM -0700, Larry Wall wrote:
> On Fri, Apr 15, 2005 at 06:04:32PM +0200, Juerd wrote:
> : No, Ucfirst it can't be, I think. And ALLCAPS is ugly. @ is taken (and
> : ugly). Suggestions?
>
> Maybe we could define an "ok" operator that suppresses only the
> *first* warn
David Wheeler wrote:
But the first person to write <[a...]> gets what's comin' to 'em.
Is that nothing (since '.' lt 'a'), or everything after 'a'?
-- Rod Adams
On Fri, Apr 15, 2005 at 12:56:14AM -0700, Mark A. Biggar wrote:
: Yes, the value 0x can be stored as either 3 byte UTF-8 string or a 2
: byte UCS-2 value, but the Unicode standard specifically says that the
: values 0x, 0xFFFE and 0xFEFF are NOT valid codepoints and should
: never appear
15/04/2005 10:35:56, Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>Nigel Sandever <[EMAIL PROTECTED]> wrote:
>
>> When a sub that closes over a variable
>
>> my $closure = 0;
>> sub do_something {
>> return $closure++:
>> }
>
>> is called from two threads, do the threads
Larry Wall wrote:
On Fri, Apr 15, 2005 at 06:04:32PM +0200, Juerd wrote:
: No, Ucfirst it can't be, I think. And ALLCAPS is ugly. @ is taken (and
: ugly). Suggestions?
Maybe we could define an "ok" operator that suppresses only the
*first* warning produced by its argument(s). Then if you get multi
Rod Adams skribis 2005-04-15 11:53 (-0500):
> Wouldn't some form of trait make more sense:
>my $sql = '...' is ok;
Depends. A unary ok operator would let you pinpoint very easily,
*without* using parens:
ok $fh.print($foo); # no warnings about print (closed fh?)
#
Aaron Sherman writes:
> Among the various ways of declaring variables, will Perl 6 have a way to
> say, "this variable is highly temporary, and may be re-declared within
> the same scope, or in a nested scope without concern"? I often find
> myself doing:
>
> my $sql = q{...};
> ...do
Isn't that what the difference between byte-level and codepoint-level access to
strings is all about. If you want to work with values that are illegal
codepoints then you should be working at the byte-level not the
codepoint-level, at least by default.
--
Mark Biggar
[EMAIL PROTECTED]
[EMAIL
On Fri, 2005-04-15 at 05:38 -0700, François PERRAD wrote:
> small mistake in [perl #34986] :
> with ICU 3.2, the library icudata.lib is renamed icudt.lib.
Thanks, applied.
-- c
Leopold Toetsch via RT wrote:
Nick Glencross <[EMAIL PROTECTED]> wrote:
This patch fixes a problem which can occur in this example:
.sub test
.const float a = 12
print a
print_newline
.end
Ah yep.
+if (t != 'P' && t != val->set)
+IMCC_fataly(inter
The following chunks behave the same in Perl 5.6 as in Perl 5.8. Notice the
output of "branching" statement modifiers vs. "looping" statement modifiers.
perl -e '$f=1; {local $f=2; print "$f"} print " - $f\n"'
# prints 2 - 1
perl -e '$f=1; {local $f=2 if 1; print "$f"} print " - $f\n"
# pr
(If anyone is able to track down aforementioned DOD/GC problems,
you'll earn my eternal gratitude.)
Can you please provide a code snippet that exhibits the error.
Just running the program gives me errors on both Linux/x86 and OS X.
Running with GC disabled works fine.
On OS X with GC e
Paul Seamons skribis 2005-04-15 11:50 (-0600):
> my %h = ;
> {
> temp %h{$_} ++ for %h.keys;
Just make that two lines. Is that so bad?
temp %h;
%h.values »++;
> %h.say; # values are incremented still
> }
> %h.say; # values are back to original values
Juerd
--
http://convolution.nl
Aaron Sherman <[EMAIL PROTECTED]> wrote:
> What I'd really like to say is:
>
> throwawaytmpvar $sql = q{...};
> throwawaytmpvar $sql = q{...};
Anything wrong with:
my $sql = q{...};
temp $sql = q{...};
temp $sql = q{...};
(Assuming C is made to work on lexicals, of cours
On Friday 15 April 2005 11:57 am, Juerd wrote:
> Paul Seamons skribis 2005-04-15 11:50 (-0600):
> > my %h = ;
> > {
> > temp %h{$_} ++ for %h.keys;
>
> Just make that two lines. Is that so bad?
>
> temp %h;
> %h.values »++;
>
For the given example, your code fits perfectly. A more commo
Brent 'Dax' Royal-Gordon skribis 2005-04-15 11:15 (-0700):
> Anything wrong with:
Yes, moving things around breaks it, as does removing the first. There
is no real dependency on the first $sql and it'd be great if declaration
wouldn't add one.
temp $sql = q{...};
my $sql = q{...};
temp $
Leopold Toetsch via RT wrote:
I think, we could be a bit more graceful here for I/N mismatch and set
for the above case the constant val->set to 'N'.
Let me redo that... I've just sent the wrong attachment which had a
typo in it ...
[This should really address rare but possible Unicode str
On Fri, 2005-04-15 at 11:21 -0500, Patrick R. Michaud wrote:
> On Fri, Apr 15, 2005 at 09:17:13AM -0700, Larry Wall wrote:
> > Maybe we could define an "ok" operator that suppresses only the
> > *first* warning produced by its argument(s). Then if you get multiple
> > warnings, you at least get
Paul Seamons skribis 2005-04-15 12:16 (-0600):
> For the given example, your code fits perfectly. A more common case I have
> had to deal with is more like this:
> my %h =
> my %other = ;
> {
> temp %h{$_} = %other{$_} for %other.keys;
Either
temp %h;
%h{$_} = %other{$_} for %other.k
>
> temp %h;
> %h{ %other.keys } = %other.values;
>
> or even
>
> temp %h{ %other.keys } = %other.values;
>
> should work well already?
Almost - but not quite.
In Perl5
perl -MData::Dumper -e '%h=qw(a 1 b 2); {local %h; $h{a}="one"; print Dumper
\%h} print Dumper \%h;
$VAR1 = {
On Fri, 2005-04-15 at 13:10, Luke Palmer wrote:
> Aaron Sherman writes:
> > Among the various ways of declaring variables, will Perl 6 have a way to
> > say, "this variable is highly temporary, and may be re-declared within
> > the same scope, or in a nested scope without concern"? I often find
> >
On Friday 15 April 2005 12:28 pm, Juerd wrote:
> temp %h{ %other.keys } = %other.values;
Oops missed that - I like that for solving this particular problem. It does
even work in Perl5:
perl -MData::Dumper -e '%h=qw(a 1 b 2); {local @h{qw(a b)}=("one","two");
print Dumper \%h} print Dumper \%h'
On Fri, Apr 15, 2005 at 07:26:56PM +0100, Nick Glencross wrote:
> +// Forbid assigning a string to anything other than a string const
> +// for now
In future, please don't use C99 comments.
(apart from that, I don't have the knowledge to comment on this patch)
Nicholas Clark
On Fri, Apr 15, 2005 at 05:12:54PM +, [EMAIL PROTECTED] wrote:
: Isn't that what the difference between byte-level and codepoint-level
: access to strings is all about. If you want to work with values that
: are illegal codepoints then you should be working at the byte-level
: not the codepoi
On Fri, Apr 15, 2005 at 11:28:31AM -0500, Rod Adams wrote:
: David Wheeler wrote:
:
: >But the first person to write <[a...]> gets what's comin' to 'em.
:
: Is that nothing (since '.' lt 'a'), or everything after 'a'?
Might as well make it everything after 'a' for consistency. One could
also vi
Paul Seamons skribis 2005-04-15 12:41 (-0600):
> In Perl5
> perl -MData::Dumper -e '%h=qw(a 1 b 2); {local %h; $h{a}="one"; print Dumper
> \%h} print Dumper \%h;
> $VAR1 = {
> 'a' => 'one'
> };
> $VAR1 = {
> 'a' => '1',
> 'b' => '2'
> };
> I'm imaging
I would like to get rid of all those implicit scopes. The only
exception would be that any topicalizing modifier allocates a private
lexical $_ scoped to just that statement. But dynamic scoping may
happen only at explicit block boundaries.
I can see the argument for the other side, where any "d
I've been working on a C-to-Parrot compiler (actually an IMC backend
for the LCC compiler), tentatively named Carrot, over the past week. It
can currently do some reasonably useful things, like running the Cola
compiler (with only a very small amount of cheating), but it has raised
a few queries:
> I'm imagining it will be different, as I expect temp to not hide the old
> thing. I'm not sure it will.
That is another good question. I just searched through the S and A's and
couldn't find if temp will blank it out. I am thinking it will act like
local. Each of the declarations my, our an
On Fri, Apr 15, 2005 at 02:38:36PM +0200, Leopold Toetsch wrote:
: I'm not quite sure, but it seems that some of the MMD functions may
: better be vtable methods:
:
: - bitwise_sh[rl]*shift by anything other then int?
: - bitwise_lsris missing generally
:
: or even just a plain opcod
On Fri, Apr 15, 2005 at 09:34:58AM -0700, Larry Wall wrote:
> It doesn't have to be the default, though. But there has to be
> some way of allowing illegal characters to be talked about, or
> you can't write programs that talk about them. It's like saying
Thoughtcrime acceptable. Doubleplusgood
Thus spake Larry Wall:
> Offhand, I guess my main semantic problem with it is that if a chdir
> fails, you aren't in an undefined location, which the new value of $CWD
> would seem to indicate. You're just where you were. Then the user
> either has to remember that, or there still has to be some
Paul Seamons skribis 2005-04-15 13:42 (-0600):
> Each of the declarations my, our and local currently set the value to
> undefined (unless set = to something).
That's not true.
use strict;
$::foo = 5;
our $foo;
print $foo; # 5
Juerd
--
http://convolution.nl/maak_juerd_blij.ht
Is there a -like thingy that is always \s+?
Do \s and match non-breaking whitespace, U+00A0?
How about:
U+0008 backspace
U+00A0 no break space (Repeated for overview)
U+1361 ethiopic wordspace
U+2000 en quad
U+2001 em quad
U+2002 en space
U+2003 em space
U
Michael G Schwern skribis 2005-04-15 13:12 (-0700):
> To be clear: Only the store operation will return undef on failure.
> Additional fetches on $CWD will continue to return the cwd.
Still breaks
$ref = \($CWD = $foo);
I'm not sure this breakage matters, but if it breaks one thing, it's
On Fri, Apr 15, 2005 at 01:12:46PM -0700, Michael G Schwern wrote:
: Thus spake Larry Wall:
: > Offhand, I guess my main semantic problem with it is that if a chdir
: > fails, you aren't in an undefined location, which the new value of $CWD
: > would seem to indicate. You're just where you were.
Pasted from pugs/examples/cookbook/01-00introduction.p6:
# XXX - question: How equal are bunches of spaces to tabs?
# -- I'd say that's a question for perl6lang
Juerd
--
http://convolution.nl/maak_juerd_blij.html
http://convolution.nl/make_juerd_happy.html
http://convolution.nl/gajigu_ju
On Fri, 2005-04-15 at 23:52 +0200, Juerd wrote:
> Well, after failure it can be cwd() but false without breaking any real
> code, because normally, you'd never if (cwd) { ... }, simply because
> there's ALWAYS a cwd.
Not always -- try removing a directory that's the pwd of another
process.
-- c
On Fri, 2005-04-15 at 17:44, Juerd wrote:
> Is there a -like thingy that is always \s+?
Not sure what that means exactly.
> Do \s and match non-breaking whitespace, U+00A0?
As I understood, Perl 6 was going to use the Unicode standard(s) to
determine the whitespacishness of each codepoint. Goin
chromatic skribis 2005-04-15 15:18 (-0700):
> > Well, after failure it can be cwd() but false without breaking any real
> > code, because normally, you'd never if (cwd) { ... }, simply because
> > there's ALWAYS a cwd.
> Not always -- try removing a directory that's the pwd of another
> process.
R
Aaron Sherman skribis 2005-04-15 18:20 (-0400):
> > Is there a -like thingy that is always \s+?
> Not sure what that means exactly.
is \s* or \s+, depending on its surroundings.
> Thankfully, NBSP (U+00A0) is not Unicode whitespace.
Thanks for sharing this information!
Juerd
--
http://convol
On Fri, Apr 15, 2005 at 11:44:03PM +0200, Juerd wrote:
: Is there a -like thingy that is always \s+?
Not currently, since \s+ is there. used to be that, but
currently is defined as the magical whitespace matcher used by :words.
: Do \s and match non-breaking whitespace, U+00A0?
Yes.
: How ab
Larry Wall skribis 2005-04-15 15:38 (-0700):
> : Do \s and match non-breaking whitespace, U+00A0?
> Yes.
That makes \s+ and \s*, and thus very useless for anything but
trimming whitespace. For splitting (including word wrapping), it'd do
exactly the wrong thing.
> : \s is said (in S05) to match
On Sat, Apr 16, 2005 at 12:46:47AM +0200, Juerd wrote:
: Larry Wall skribis 2005-04-15 15:38 (-0700):
: > : Do \s and match non-breaking whitespace, U+00A0?
: > Yes.
:
: That makes \s+ and \s*, and thus very useless for anything but
: trimming whitespace. For splitting (including word wrapping),
On Sat, Apr 16, 2005 at 12:11:24AM +0200, Juerd wrote:
: Pasted from pugs/examples/cookbook/01-00introduction.p6:
:
: # XXX - question: How equal are bunches of spaces to tabs?
: # -- I'd say that's a question for perl6lang
This seems to be singularly short on context, but if it has to do w
I thought we had just established that nbsp is not in Unicode¹s definition
of whitespace. So why should \s match it?
On 2005-04-15 18:56, "Larry Wall" <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 16, 2005 at 12:46:47AM +0200, Juerd wrote:
> : Larry Wall skribis 2005-04-15 15:38 (-0700):
> : > : Do
More questions stemming from cookbook work... Decimal Comparisons:
The most common recipe around for comparisons is to use sprintf to cut
the decimals to size and then compare strings. Seems ugly.
The non-stringification way to do it is usually along the lines of:
if (abs($value1 - $value2) < a
On Friday 15 April 2005 3:27 am, Larry Wall wrote:
> On Fri, Apr 15, 2005 at 03:27:27AM +0300, Roie Marianer wrote:
> : > %hash<< a $key_b c >> :key<< a $value_b c >>
> : > %hash« a $key_b c »:key« a $value_b c »
> :
> : Just to be certain, these are both equivalent to
> :
> : @hash{'
At 16:18 -0700 4/15/05, gcomnz wrote:
>More questions stemming from cookbook work... Decimal Comparisons:
>
>The most common recipe around for comparisons is to use sprintf to cut
>the decimals to size and then compare strings. Seems ugly.
>
>The non-stringification way to do it is usually along th
Hola...
The code used to generate pugs smoke HTMLs (like
http://nothingmuch.woobling.org/pugs_test_status/ - warning around
800K), was refactored into two perl (5) modules, now (that is, when
your mirror has synched) available on the CPAN.
This code is authored by many of the pugs authors. If you
On Fri, Apr 15, 2005 at 11:52:38PM +0200, Juerd wrote:
> > becomes an unverifiable operation. You have to use chdir() if you want to
> > error check and $CWD is reduced to a "scripting" feature.
>
> Well, after failure it can be cwd() but false without breaking any real
> code, because normally,
1 - 100 of 108 matches
Mail list logo
