Re: Contextual Variables

On Fri, May 15, 2009 at 07:16:45PM -0500, John M. Dlugosz wrote: > Reading through S02, I see that contextual variables has changed in the > last year. It appears that contextual and global variables have been > unified. So, the + twigil is no more? > > I assume the point is that any supposed

Re: Right place for discussions?

On Fri, May 15, 2009 at 07:21:38PM -0500, John M. Dlugosz wrote: > Looking at recent traffic, there is more on tickets and checkins, so any > actual "forum" messages are lost among them. Should "discussion" be > separate? Generally discussion of specs should be on perl6-langauge, though of c

Re: Right place for discussions?

I should also point out that a lot of the brainstorming and thrashing out actually happens on IRC, specifically #perl6 at irc.freenode.net. (Though the s2n ratio is highly variable there, as on any IRC channel.) It is logged at http://irclog.perlgeek.de/perl6/today. There is usually someone around

Re: [perl #65782] [Bug] rakudo silently ignores remaining code after unmatched pod

On Tue, May 19, 2009 at 10:24:41AM -0500, Patrick R. Michaud wrote: : On Tue, May 19, 2009 at 12:30:53AM -0700, Ahmad Zawawi wrote: : > Given the following: : > : > "1".say; : > =begin pod : > =end pod1 : > "2".say; : > : > The output is only "1" but should be "1\n2" or at least a runtime : > err

Re: [perl #65878] Rakudo shouldn't allow metaops with the same modifier twice in a row

On Thu, May 21, 2009 at 02:56:23AM -0700, Carl Mäsak wrote: : # New Ticket Created by "Carl Mäsak" : # Please include the string: [perl #65878] : # in the subject line of all future correspondence about this issue. : # http://rt.perl.org/rt3/Ticket/Display.html?id=65878 > : : : rakudo: sub i

Re: [perl #65942] Missing %*ENV values are defined, but don't exist

On Sun, May 24, 2009 at 12:08:58PM -0700, yary wrote: : > I don't recall if defined autovivifies, but assuming it does that would make : > sense. : : Agreed that if defined autovivifies, it explains observed behavior in : current rakudo. But should "defined" autovivify? That goes against my : intu

Re: [perl #65878] Rakudo shouldn't allow metaops with the same modifier twice in a row

On Thu, May 21, 2009 at 07:20:57PM +0200, Gianni Ceccarelli wrote: : On 2009-05-21 Larry Wall wrote: : > : rakudo: sub infix:($a,$b) { $a ~ '-' ~ $b }; sub : > : infix:($a,$b) { $a ~ '_' ~ $b }; say 'x' R 'y'; say 'x' RR 'y'; :

Re: [perl #66538] [BUG] Rakudo falls in the infinite loop in Range with non-ascii

On Mon, Jun 15, 2009 at 12:17:41PM -0700, Patrick R. Michaud via RT wrote: : A related question may be: what should the following produce? : : 1..4 :by(0) Same as 1 xx *, I suppose. I don't know if the range would be smart enough to report itself as an infinite iterator, so a mostly eager d

Re: [perl #66538] [BUG] Rakudo falls in the infinite loop in Range with non-ascii

On Mon, Jun 15, 2009 at 12:17:41PM -0700, Patrick R. Michaud via RT wrote: : More to the point, if you want to cycle through a range of codepoints, : you probably want: : : map { .chr }, 44032..45208; Well, almost certainly you'd want it in hex, but yes. : I agree that the string form of the

Re: [perl #66606] Statmenet modifier's "implied" lexical scope hides my declaration

We now spec a simple temporization (doesn't even have to be implemented using "temp") for topicalizing statement modifiers. See latest S04. Larry

Re: Command-line args (weekly contribution to P6)

On Wed, May 26, 2010 at 07:22:36AM -0700, jerry gay wrote: : On Wed, May 26, 2010 at 00:53, Moritz Lenz wrote: : > The spec doesn't elaborate on how the short args are specified in the : > signature of MAIN. I see two possible approaches (that don't contradict): : > : > 1) one renames them in the

Re: [perl #125391] Wrong order with %% $=.*

Since the sort is stable, I believe it suffices simply to sort on the .to instead of the .from. Larry

Re: [perl #129346] [BUG] Whatever being called on where-blocked subroutine cannot handle the sigilless values correctly

On Fri, Sep 23, 2016 at 11:42:20PM -0700, Itsuki Toyota wrote: : # New Ticket Created by Itsuki Toyota : # Please include the string: [perl #129346] : # in the subject line of all future correspondence about this issue. : # https://rt.perl.org/Ticket/Display.html?id=129346 > : : : See the fol

Re: [perl #129884] Strange behaviour on "say".

On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote: : Actually, I just tested the code and on my machine it always outputs : "test". The only difference between uncommenting "say 'run'" is that : it'll output "run" once at the end - or not. : : So now I'm wondering what i did differentl

Re: [perl #129884] Strange behaviour on "say".

On Sat, Oct 15, 2016 at 09:59:01PM +0200, Timo Paulssen wrote: : Actually, I just tested the code and on my machine it always outputs : "test". The only difference between uncommenting "say 'run'" is that : it'll output "run" once at the end - or not. : : So now I'm wondering what i did differentl

Re: Bundles

On Tue, Sep 07, 2004 at 07:39:49PM -0400, Dan Sugalski wrote: : You've got things a bit turned around I think. Parrot's the engine. : It provides the services, runs the code, handles the environment, and : generally manages stuff. If you want, think of it as a combination : CPU, OS, low-level de

Re: Current state?

On Wed, Sep 08, 2004 at 07:33:45AM -0600, Patrick R. Michaud wrote: : We're in the beginning stages of building a basic perl 6 grammar engine : (i.e., probably without p6 closures) that compiles to parrot and handles : basic optimizations. I wonder whether, in the absence of closures, we'll have

Re: Current state?

On Wed, Sep 08, 2004 at 02:18:38PM -0400, JOSEPH RYAN wrote: : b.) The A5 stuff is definitely the most stable part of the Perl6 : design. As far as I know, it hasn't really changed much at all over : the past 2 years. You could probably work directly off of A5 and : S5 without having to worry if

Re: Current state?

On Wed, Sep 08, 2004 at 06:37:20PM +, Herbert Snorrason wrote: : The synopses are kept up to date, though, aren't they? That's the theory, though some of them have aged a bit. Updates are in the works, along with various new synopses, including some for apocalypses that haven't been written.

Re: Current state?

On Wed, Sep 08, 2004 at 02:47:24PM -0400, JOSEPH RYAN wrote: : We tried that as an optimization in the prototype : Perl6 compiler. It ended up being a really really : really bad idea because the grammar backtracked like : a madman. It might be workable if we can infuse : 's in every location

Re: Current state?

I'd suggest looking at the t/op/re_tests file from Perl 5. It's based on the test suite that originally came with Henry Spencer's regular expression package. It would, of course, need to be translated and extended, but it contains a lot of torturous tests for the standard rx behavior. And it's a

Re: Current state?

On Tue, Sep 14, 2004 at 08:13:13PM +0200, James Mastros wrote: : Of course, this is really language design -- Larry, you listening? Sure, I'm listening, but what's the point when I agree with everyone. :-) I agree that the default should be the current outer language. I agree that the default o

S5 updated

I've been working at updating the various synopses on dev.perl.org. In particular, you folks might like to know that the regex synopsis at http://dev.perl.org/perl6/synopsis/S05.html is no longer two years out of date. :-) Larry

Re: Current state?

On Fri, Sep 17, 2004 at 08:19:37AM -0600, Patrick R. Michaud wrote: : I'm going to go with a syntactic shortcut for the time being, albeit : something more complex than the suggestion above. I don't want to force : people to make multi-line closures. It will probably look for matching : braces, s

Re: Current state?

On Sat, Sep 18, 2004 at 08:36:06AM -0700, Larry Wall wrote: : I think in the long run we'll have those inner compilers that know how to : stop themselves and can be handed a closure, and those that don't know how : to stop, and must be spoonfed the right amount, which is almost always

Synopses updated on dev.perl.org

I finally managed to get the newest synopses and apocalypses up on dev.perl.org, so please consider my www.wall.org directories deprecated. If you haven't had a chance to peruse the synopses lately, now would be a good time. If you read them when they came out on www.wall.org, there have been som

Re: PGE tests wanted (was P6GE tests wanted)

On Sat, Dec 18, 2004 at 12:16:31PM +0200, Markus Laire wrote: : Patrick R. Michaud wrote: : >>Larry mentioned 're_tests' file from perl5-source. Is anyone working on : >>it currently? I could make a simple script to convert at least some of : >>it to this pge-testing format which uses p6rule_* :

Hyphenated rule names [Was: Perl 6 Summary for 2004-12-06 through 2004-12-20]

On Mon, Dec 20, 2004 at 09:52:32PM -0500, Matt Fowles wrote: : Much churning went on and it seems that multiple different : (but identically named) rule captures can now be performed by adding : information after a dash ala " ". Actually, much churning is still going on in both @Larry

Re: thoughts about types, and possible syntax for code as comment

On Thu, Jan 06, 2005 at 11:07:47PM +0100, Stéphane Payrard wrote: : To get an huffmanized name and a clear one, I would like some support syntax: : : sub canon( $subjet as $s , $complement as $c ) { : # code with lots of $s and $s : } Aliasing can currently be done with the binding oper

Re: parsing ok((2+3)==5)

On Tue, Mar 01, 2005 at 07:22:08PM -0500, Abhijit Mahabal wrote: : Hmm. I wonder if that introduces more bugs itself. Is the following legal? : f ($x) It is legal if f has been predeclared, in which case it parses as a list operator, and ($x) is its first argument. That is, f ($x),2 w

Re: [PUGS] Bugs

On Sat, Mar 05, 2005 at 12:04:16AM +0800, Autrijus Tang wrote: : The double evaluation bug has been fixed today. It was result of a : misunderstanding of the role of $_ when the subroutine body does : not mention $_, but makes use of slurpy arrays (as is the default with : @*_), and has no invocan

Re: Method call parsing

On Sun, Mar 06, 2005 at 03:15:23PM -0700, Luke Palmer wrote: : But this allows the syntax '$x.foo $y', that is, an argument to a method : call without parentheses. This isn't a big deal, and could even be : construed as a feature, if it weren't for: : : for %hash.keys { ... } : : Which is mi

Re: array interpolation implemented; a question

On Sun, Mar 06, 2005 at 12:30:43PM -0500, Garrett Rooney wrote: : Autrijus Tang wrote: : >On Sat, Mar 05, 2005 at 02:39:06PM -0700, Luke Palmer wrote: : > : >>Garrett Rooney writes: : >> : >>>Garrett Rooney wrote: : >>> : >>> : Assuming the spec is correct, here's a patch to add some more tests

Re: [PUGS] patch - few hyperops

On Fri, Mar 11, 2005 at 12:53:45PM +0200, Markus Laire wrote: : This is my first patch ever, so could someone check if this is OK or : not. This only adds few hyperops, as I'm not 100% sure if this is the : right way to do it. It is good to have a general mechanism for wrapping any binary op up

Re: [PUGS] patch - few hyperops

On Sat, Mar 12, 2005 at 03:14:33PM +0800, Autrijus Tang wrote: : Oh, btw, is there some more documents for the &statement:<> level : parsing and handling somewhere, or at least a general overview of : how those things are defined? :) Below is an excerpt of something I sent Patrick last month that

Re: [Pugs] Closing a file handle surprised the heck out of me

On Mon, Mar 14, 2005 at 10:58:00PM +1100, Andrew Savige wrote: : Given this Pugs program, t.p6: : : my $fh = open(@ARGS[0]); : my @lines = =$fh; : $fh.close(); : for @lines { print"$_" } : : running: : : pugs t.p6 t.p6 : : produces no output. Move $fh.close() to after the for : loop and all is

Re: int("0x123") == int(0x123) ?

On Tue, Mar 15, 2005 at 11:09:11PM +0800, Autrijus Tang wrote: : Currently Pugs numifies hexadecimal and octal strings as if they : are literals; that means "0x123" and "0o456" all work as expected. : Is that an acceptable treatment? It's okay by me. The restriction on not autoconverting hex and

Re: Analysis of operator "?? ::"

On Wed, Mar 16, 2005 at 01:35:12AM +0800, Autrijus Tang wrote: : that is, it reads everything between ?? and ::, allowing only : tight operators That is correct. Larry

Re: int("0x123") == int(0x123) ?

On Wed, Mar 16, 2005 at 02:57:36AM +0800, Autrijus Tang wrote: : So, between the two consistencies, do you think that the more DWIMmy : one of parsing "0o123" is more helpful? I'll implement it tomorrow : if that's the case. :) Yes, I do. That was one of the main reasons for switching to the les

Re: [Pugs] short-circuit operators

On Wed, Mar 16, 2005 at 01:30:10PM +0800, Autrijus Tang wrote: : On Wed, Mar 16, 2005 at 12:31:05PM +1100, Andrew Savige wrote: : > Ferreting around in the #perl6 logs I noticed an acknowledgement : > that short-circuiting is "borken" as at 15 Maart. Oh well, time : > for the "mad golfer" to dust o

Re: [Pugs] short-circuit operators

On Wed, Mar 16, 2005 at 05:33:04PM +0800, Autrijus Tang wrote: : Also, how does that philosophy fit with the bare thunking in array : slices, as listed in A05? : : @3d_slice = @array[ !($_ % 2) ; 0..9:3; ?test($_) ]; If I recall, the discussions around S9 indicated that it might be a bad ide

Re: [Pugs] Some experiments with the for loop

On Wed, Mar 16, 2005 at 06:52:31PM +1100, Andrew Savige wrote: : # length() and bytes() seem not implemented yet (?) ... And length will never be implemented because that word is now taboo, because it is not specific enough as to units in a Unicode world. More specific methods are now used:

Re: [Pugs] short-circuit operators

On Wed, Mar 16, 2005 at 11:46:46AM -0700, Luke Palmer wrote: : Markus Laire writes: : > Larry Wall wrote: : > >Since it's not a problem for syntax that can be recognized at compile : > >time, your slice above might be allowed if you "declare" the thunks : > >wi

Re: [Pugs] Stumbled into another Pugs sand trap (indirect object call I think)

On Fri, Mar 18, 2005 at 03:27:04PM +0800, Autrijus Tang wrote: : On Fri, Mar 18, 2005 at 12:25:26AM -0700, Luke Palmer wrote: : > Of course not. &infix: refers to the infix Y operator, but you need : > the hashy subscript. : : So, what is the full name for the operator in the symbol table? :) %:

Re: [Pugs] Stumbled into another Pugs sand trap (indirect object call I think)

On Fri, Mar 18, 2005 at 04:06:21PM -0700, Luke Palmer wrote: : Larry Wall writes: : > %::{'&infix:'}, I suspect. : : I suspect that's a bad idea. What about &infix:{'<'}? Well, one could go with &infix:«<» in that case, but yes, one could alwa

Re: Best way to slurp a file in Perl 6

On Sat, Mar 19, 2005 at 11:03:40PM +1100, Andrew Savige wrote: : --- Autrijus Tang wrote: : > On Fri, Mar 18, 2005 at 09:35:59PM +1100, Andrew Savige wrote: : > > What is the best way in Perl6/Pugs to slurp a file? : > : > You use the slurp() primitive, implemented as r875. :) : : Thanks. I teste

Re: Pugs Bugs

On Tue, Mar 22, 2005 at 05:32:04PM -0500, Stevan Little wrote: : Basically, pugs does not seem to correctly parse the single quoted : string 'test\' That is not a single-quoted string. That's the beginning of a single-quoted string. All parsing in Perl 6 is left-to-right, without "lookaheads" f

Re: Questions regarding s/// and subst?

On Wed, Mar 23, 2005 at 11:14:16AM -0500, Stevan Little wrote: : Is subst an object/type? : Or is it a method of the Str object? I suspect it's just a method, and the ~~ binding of s/// is merely syntactic sugar for the method call. : If it is an object ... : : Does s/// produce a su

Re: [Pugs] Writing tests that run pugs ($^X or equivalent would seem handy)

On Thu, Mar 24, 2005 at 01:17:40PM +0800, Autrijus Tang wrote: : As of r1079, there is $?EXECUTABLE_NAME (that is, $^X in perl5) and : $?PROGRAM_NAME (that is, $0 in perl5). Note that those two things : are unspecced -- I just pulled them out from perlvar. I'd also note the $*EXECUTABLE_NAME migh

Re: BEGIN {}

On Fri, Mar 25, 2005 at 02:52:51PM +0800, Autrijus Tang wrote: : So, as now Pugs generates PMC code that makes mandel.p6 run : faster than Perl 5 (http://use.perl.org/~autrijus/journal/23829), : I'm pondering this BEGIN{} mess that Pugs had not dealt with. : : Consider this program, example.p6: :

Re: precedence of "return"

On Fri, Mar 25, 2005 at 03:47:43PM -0800, Greg Buchholz wrote: : : I'm wondering if the precedence of the "return" keyword isn't wrong : in pugs. In the code below, fibo2 works as I'd expected, fibo returns : nothing. (If this is expected behavior, I'd apppreciate someone : pointing me to TF

Re: [Pugs] A couple of string interpolation edge cases

On Sat, Mar 26, 2005 at 03:32:18PM +1100, Andrew Savige wrote: : I stumbled across a couple of interesting quote interpolation : edge cases: : : Case 1 : -- : : # cat ttt.p6 : my $x = "{"; : : # pugs ttt.p6 : : unexpected end of input : expecting "\"", "$!", "$/", "\\" or block : NonTerm So

S28ish [was: [Pugs] A couple of string interpolation edge cases]

On Sat, Mar 26, 2005 at 02:11:29PM +0800, Autrijus Tang wrote: : On Fri, Mar 25, 2005 at 10:03:45PM -0800, Larry Wall wrote: : > Hmm, well, if it got that far. Given strict being on by default, : > this particular example should probably just die on the fact that $" : > isn

Re: S28ish [was: [Pugs] A couple of string interpolation edge cases]

On Sat, Mar 26, 2005 at 03:37:41AM -0700, Luke Palmer wrote: : > $! will be a legal variable name. $/ is going away, : : By which you mean that $/ is turning into a special $0. I'd say that $0 is a specialization of $/, but yes, basically, they both represent the current match result, albeit di

Re: Pugs IO Bugs (?)

On Tue, Mar 29, 2005 at 08:37:02PM -0700, Luke Palmer wrote: : Stevan Little writes: : > : > On Mar 29, 2005, at 8:38 AM, Luke Palmer wrote: : > >Hmm... I believe that the behavior in this case is undefined. It sure : > >would be nice if it worked, but you see: : > > : > >for =$fh -> $line {

Re: Pugs Bug

On Sun, Apr 03, 2005 at 05:28:44PM +0800, Autrijus Tang wrote: : On Sat, Apr 02, 2005 at 09:32:12PM -0500, Stevan Little wrote: : > I was writing tests for split(, ) and I stumbled upon this : > bug: : > : > pugs -e 'split(rx:perl5//, "not good")' : > : > Will go into an infinite loop. I also tr

Re: More Pugs Bugs

On Tue, Apr 05, 2005 at 09:22:29PM +0800, Autrijus Tang wrote: : On Mon, Apr 04, 2005 at 09:01:20PM -0400, Stevan Little wrote: : > eval 'sub foobar { return if 1; }'; : : I've fixed everything except this. I'm not exactly sure how the postfix : form of "if" is supposed to work here, because the

Re: More Pugs Bugs

On Wed, Apr 06, 2005 at 12:32:37AM +0800, Autrijus Tang wrote: : On Tue, Apr 05, 2005 at 08:24:42AM -0700, Larry Wall wrote: : > That's why there's a statement_control:, and there's a : > statement_modifer:, but there's no prefix:. If you see : > a statement

Re: [pugs] several questions

On Mon, Apr 11, 2005 at 07:11:35AM +1000, Andrew Savige wrote: : > "my(@array)=qw(1 2 3);" gives error. "my @array=qw(1 2 3);" works. Is it : > the right behaviour? Both worked well with Perl 5. : : qw(1 2 3) is now spelled <1 2 3> I think. qw should also still work as an abbreviation for q:w.

Re: [pugs] regexp ignore case

On Thu, Apr 14, 2005 at 08:58:47AM -0600, Paul Seamons wrote: : I would think that :p5 should behave as perl5 does by default. That would : mean that /x and /s aren't on by default (for p5). I'm inclined to agree. Just as a heads up, I'm thinking of changing :perl5/:p5 to :Perl5/:P5 just to dif

Re: [pugs] regexp ignore case

On Fri, Apr 15, 2005 at 01:25:24AM +0800, Autrijus Tang wrote: : Okay. In that case, how about making Perl5ish adverbs work when :P5 is : specified? I have just checked in some code to make this work: : : rx:P5:i:m:s:x:g/.../ : : Does it make sense to you? That means that we either have to

Re: [pugs] Quoting constructs

On Thu, Apr 14, 2005 at 10:04:42PM +0300, Roie Marianer wrote: : I did hit a snag with %hash and :key notation for hashes and : pairs; I'm not sure how to make them interpolate, so for now they just don't. Do you mean the behavior of "%hash" ":key" or %hash< a $key_b c > :key< a $val

Re: [pugs] Quoting constructs

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{'a', $key_b, 'c'} key => ['a', $value_b, 'c'] : : in Perl 5, righ

Re: [pugs] regexp "bug"?

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

Re: [pugs] regexp "bug"?

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

Re: [pugs] Quoting constructs

On Sat, Apr 16, 2005 at 03:14:50AM +0300, Roie Marianer wrote: : I actually knew that, but in my head $key_b and $value_b were single words. : But according to S02, the interpolation is protected by quotes. That is, if : $key_b is q0/printf "Hello, world\n" or die"/, that's four words, correct? O

Re: PugsBugs: Weird behavior of shift

On Mon, Apr 18, 2005 at 12:08:36AM -0400, Stevan Little wrote: : These examples: : : pugs -e 'say shift [1, 2, 3].shift' : pugs -e 'say shift([1, 2, 3].shift)' : pugs -e 'say shift([1, 2, 3]).shift' : : do not ever return, but yet does not seem to chew up the CPU either. I don'

Re: Push and Pop on Infinite lists

On Sun, Apr 17, 2005 at 11:33:45PM -0400, Stevan Little wrote: : I am working on edge cases and error cases for some of the t/builtin/ : tests. : : I know its a silly thing to do, but how should push and pop behave with : (0 .. Inf) lists? : : I read through this thread: : http://www.mail

Re: When scoping

On Wed, May 04, 2005 at 11:00:31PM -0600, Luke Palmer wrote: : What should the output of this be: : : given "hello" { : when /hello/ { : say "One"; : when /hello/ { say "Two"; } : when /hello/ { say "Three"; } : continue; : } :

Re: When scoping

On Wed, May 04, 2005 at 11:00:46PM -0700, David Wheeler wrote: : On May 4, 2005, at 22:31 , Larry Wall wrote: : : >given "hello" { : >when /hello/ { : >say "One"; : >if /hello/ { say "Two"; } : >if /he

Re: Undef issues

On Tue, May 24, 2005 at 10:53:59PM +1000, Stuart Cook wrote: : I'm not sure whether this behaviour is supposed to be changing. It is. I think we decided to make the value undef, and the function undefine(). (But these days most values of undef really ought to be constructed and returned (or thro

Re: loop/do {...} while EXPR;

On Mon, May 30, 2005 at 01:42:40PM +, Luke Palmer wrote: : Because do {...} is a part of the language, while or no while. Perl 6 : is supposed to die if you say do {...} while, which isn't implemented : in pugs yet. In particular, we'd like "do {...} while" to die because do {...} is now defi

Re: What the heck is... wrong with Parrot development?

On Mon, Jun 06, 2005 at 04:31:01PM +0200, anonymous coward wrote: : It's a funny old world... : wrote Dan Sugalski on June 04, 2005 in his Squawks of the Parrot blog. : Go and see: . : : Hence the subject. : : What the heck is wrong with Parrot

Re: How to write a self.pm (Re: method calls on $self)

On Tue, Jul 12, 2005 at 10:17:01AM +0800, Autrijus Tang wrote: : On Mon, Jul 11, 2005 at 06:29:28PM -0700, Larry Wall wrote: : The obvious thought is to have yet another magical, $^H like flag, to : denote the current dialect. If it is set, then the parser can emit : .method as $_.method, instead

Re: How to write a self.pm (Re: method calls on $self)

On Tue, Jul 12, 2005 at 12:36:23PM +0800, Autrijus Tang wrote: : On Mon, Jul 11, 2005 at 09:04:54PM -0700, Larry Wall wrote: : > On Tue, Jul 12, 2005 at 10:17:01AM +0800, Autrijus Tang wrote: : > : On Mon, Jul 11, 2005 at 06:29:28PM -0700, Larry Wall wrote: : > : The obvious thought is to

Re: creating threas in BEGIN

On Thu, Jul 14, 2005 at 04:32:13PM +0100, Nicholas Clark wrote: : How will the perl6 compiler cope with people creating threads inside : BEGIN blocks? Probably break, if they meant INIT. I can't think of a static way to detect that offhand, so I'm okay if we just call it erroneous. Or maybe there

Re: Whitespace

On Thu, Aug 04, 2005 at 09:29:21PM +0400, Andrew Shitov wrote: : in fact, that is exactly : : (print.getArgument(3) * 3); the same as above. : : so why not 'print($x)' == 'print ($x)' ;-) Because most people's expectations diverge from yours, actually, and we got tired of answering the FAQ.

Re: Hoisting lexical declarations

On Mon, Aug 01, 2005 at 02:06:28AM +0800, Autrijus Tang wrote: : Pugs did not support inline variable declarations, largely because the problem : caused by this construct: : : { : say "values of β will give rise to dom!"; : $x = $x + my $x if $x; : #1 #2 #3#4 :

Re: Rough thoughts on the Object Space

On Wed, Oct 26, 2005 at 12:36:57PM -0400, Stevan Little wrote: : This is a very rough and high level view, and ignores little details : like macros, BEGIN blocks, etc. Yes, Perl 5 is conceptually a 3-pass compiler, but the passes have to be interwoven to do the "literate compilation" thing that

Re: The meaning of \n and \N in rules

On Fri, Nov 04, 2005 at 09:53:07AM -0600, Patrick R. Michaud wrote: : Synopsis 5 says that "C<\n> now matches a logical (platform independent) : newline not just C<\012>". But the devil is in the details, and I'm : wanting confirmation (or discussion) of the details on \n so I can : implement it

Re: [] and () on rule modifiers

On Fri, Nov 04, 2005 at 01:26:14PM -0600, Patrick R. Michaud wrote: : A05 currently says: : : The first space in : : /[:w foo bar]/ : : matches \s* before "foo". That's usually what you want, : but if it's not what you want, you have a little problem. : Unfortunately y

Re: Octal in p6rules (and strings)

On Mon, Nov 07, 2005 at 10:51:59AM -0600, Patrick R. Michaud wrote: : In p6rules, how should specify characters (glyphs, bytes, whatever) : using octal notation? : : Currently S02 says that integer constants in octal are written with : as "0o" prefix (as in 0o123), just as we would use the "0x" pr

Re: [Pugs] Change in behaviour of reversing lines in a file (golf example)

On Sun, Nov 06, 2005 at 11:31:37PM +1100, Andrew Savige wrote: : On revisiting the old p6 golf example programs of *cough* six : months ago, I noticed they all still worked save one: : : [=<>].reverse.print : : This used to reverse the lines in a file, but now prints the : lines unreversed and wi

Re: Octal in p6rules (and strings)

On Mon, Nov 07, 2005 at 02:18:24PM -0600, Patrick R. Michaud wrote: : Having a shortcut for seems like a very good idea; it : certainly makes things a lot simpler for the optimizer. However, : a reminder that A05 says that angles can be used as a bracketing : construct as in C<< \x<0a> >>, so we

Re: Octal in p6rules (and strings)

On Mon, Nov 07, 2005 at 02:18:24PM -0600, Patrick R. Michaud wrote: : Ick, \d65 in a pattern looks really odd to me. I'll register my : distaste for this one message, and then I'll have to take a stiff : drink or something before I can bring myself to implement it. :-| I suppose we could even go

Re: Octal in p6rules (and strings)

On Mon, Nov 07, 2005 at 02:47:05PM -0600, Patrick R. Michaud wrote: : > : But for the :w issue, we can always solve it with the colon: : > : : > : \d:065 = A digit (cut) followed by "065" : > : > That doesn't extend to \d:woot, of course... : : It doesn't? I mean, isn't that a digit fol

Re: Octal in p6rules (and strings)

On Tue, Nov 08, 2005 at 10:55:05AM -0500, Matt Fowles wrote: : Patrick~ : : On 11/8/05, Patrick R. Michaud <[EMAIL PROTECTED]> wrote: : > On Tue, Nov 08, 2005 at 12:57:18PM +, [EMAIL PROTECTED] wrote: : > > "Patrick R. Michaud" <[EMAIL PROTECTED]> wrote: : > > :And we also get \d:0123 as a che

Re: context matters

On Tue, Nov 15, 2005 at 12:32:38PM -0600, Patrick R. Michaud wrote: : On Tue, Nov 15, 2005 at 10:26:05AM -0800, jerry gay wrote: : > > Thus, while PGE::Match currently defines a C<__get_pmc_keyed_int> : > > method, it's doesn't yet define a C<__get_string_keyed_int> method. : > > So, a statement li

Re: Table of Perl 6 "Types"

On Tue, Jan 03, 2006 at 07:34:41PM -0500, Stevan Little wrote: : Hello again, : : Chip pointed out to me that my post was severely mangaled because it : was too wide, so I have reformatted to fit within 70 columns, hope : this works better. : : NOTE: I realize that this format may be entirely

pre0 non-smoke

Here's results of r8894 on up-to-date Fedora Core 4 with embparrot r11392. Other the usual embparrot rules breakage, is looking pretty clean here even with bleadparrot. All the failures below look like rules coredumps to me, including the undef.t one. Larry Failed Test Sta

embparrot still has two failures

Failed Test Stat Wstat Total Fail Failed List of Failed --- t/rules/from_perl6_rules/array_ca 18 460845 10 22.22% 41-45 t/rules/from_perl6_rules/named_ca 18 460826 48 184.62% 3-2

Re: Macros?

After a little more cleanup, S06 now reads: =head2 Macros Macros are functions or operators that are called by the compiler as soon as their arguments are parsed (if not sooner). The syntactic effect of a macro declaration or importation is always lexically scoped, even if th

Re: embparrot still has two failures

On Thu, Feb 02, 2006 at 10:58:39PM -0500, Uri Guttman wrote: : >>>>> "LW" == Larry Wall <[EMAIL PROTECTED]> writes: : : LW> pugs -V: : : LW> This is Perl6 User's Golfing System, version 6.2.11, February 1, : LW> 2005 (r8945) built for i386-linux

Re: use of parrot built source tree in pugs

On Thu, Feb 02, 2006 at 08:18:14PM -1000, Beau E. Cox wrote: : Hi - : : When making pugs, I know that the following env must be : setup to imbed parrot: : : ... : export PUGS_EMBED="perl5 parrot" : export PARROT_PATH="/the/parrot/built/source/tree" : ... : : Is the parrot source tree only needed

Re: tokenizer hints, supporting delimited identifiers or symbols

say $::; Larry

Re: tokenizer hints, supporting delimited identifiers or symbols

On Tue, Feb 07, 2006 at 03:28:05PM -0800, Larry Wall wrote: : say $::; Or you can use a symbolic ref with a constant string: $::('x y'); The compiler knows it's a constant. And it's even implemented in Pugs. But my thinking on the ::<> form is that it derives fro

Re: tokenizer hints, supporting delimited identifiers or symbols

On Tue, Feb 07, 2006 at 03:49:36PM -0800, Darren Duncan wrote: : At 3:28 PM -0800 2/7/06, Larry Wall wrote: : >say $::; : >Larry : : My mistake. When I read Synopsis 2 I had interpreted the text more : narrowly than what I was looking for. So for now I retract my : request. Well, it

Re: tokenizer hints, supporting delimited identifiers or symbols

On Wed, Feb 08, 2006 at 12:26:52AM +, Luke Palmer wrote: : On 2/7/06, Larry Wall <[EMAIL PROTECTED]> wrote: : > $MY::{'x y'} : > $MY:: # same thing : > MY::<$x y> # same thing : : Er, aren't we obscuring the meaning of <>

Re: tokenizer hints, supporting delimited identifiers or symbols

On Tue, Feb 07, 2006 at 03:54:07PM -0800, Larry Wall wrote: : On Tue, Feb 07, 2006 at 03:28:05PM -0800, Larry Wall wrote: : : say $::; : : Or you can use a symbolic ref with a constant string: : : $::('x y'); : : The compiler knows it's a constant. And it's even imple

Re: Infix macro := reparsing the LHS?

On Wed, Apr 19, 2006 at 10:08:29PM +0800, Audrey Tang wrote: : Not sure if this is p6l or p6c... Fallback to the latter. :) : : In this line: : :[Dog ::T $ ($x) where 1, *$, [EMAIL PROTECTED] := moose(); : : the left hand side is probably not a valid Perl 6 expression, yet : according to the

  1   2   3   >