Re: Naming debate- what's the location for it?

Just Mu would be an amusing Perlish pun based on Muttsu... Making the interpretation either Perl "six" or Perl "most undefined". I like yary's idea too. Frankly, if Perl had an identity, I would not care about the name. I feel like it lacks that right now. -- Aaro

Re: Naming debate- what's the location for it?

g an explicit number. Normally, I'd recommend Latin, but Perl Sex is probably not where anyone wants to go... Roku is Japanese, but also the name of a popular device, and thus confusing... -- Aaron Sherman, M.: P: 617-440-4332 // E: a...@ajs.com Toolsmith, developer, gamer and life-long stud

Re: CALL-ME vs. Callable

ith a change to the way Callable and calling work. I'm not suggesting that the latter is bad, but it seems to be a patch around a problem in the former... Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long student. On M

Re: CALL-ME vs. Callable

So, you said that the problem arises because NQP does something non-obvious that results in this error. Can you be clear on what that non-obvious behavior is? It sounds to me like you're addressing a symptom of a systemic issue. Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and G

Re: CALL-ME vs. Callable

Fair points, all. I do think, though that if the concern is really with "the 4 cases when nqp hauls a CALL-ME out of its bowels" then that's what should be addressed... Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, game

Re: CALL-ME vs. Callable

Role-based testing seems very perl6ish. I'd suggest the role name be "Invocable" with much the sort of signature as you've described. That being said, I don't think that the current error is terrible. It clearly shows that the issue is with the attempt to invoke a Boo

Re: Is this a bug?

Thank you. Silly me, thinking "this is so simple I don't need to run it through the command-line to test it." :-) Anway, yeah, say $_ for reverse lines Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and li

Re: Is this a bug?

. But remember that any {} around code creates a Block in Perl 6, and a Block is a first-class object. If you ask say to print a Block, it will quite happily try to do that. Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and li

Re: This seems to be wrong

"for @inputs.map( .prefix:<+> ) {...}" That's spelled: "for @inputs>>.Int -> $i { ... }" You can also use map, but it's slightly clunkier: "for @inputs.map: .Int -> $i { ... }" Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email

Re: Justification for the "reversed" instruction format

q', 'k', :by(2); say flip-counter 3.7, 1, :by(2); $ perl6 foo.p6 (2 4 6 8 10) (k m o q) Cannot resolve caller counter(Int, Rat, Int); none of these signatures match: (Int $start, Int $end, :$by = 1) (Str $start, Str $end, :$by = 1) in block at foo.p6 line 3 Aaron

The use of $!attr vs self.attr in core libraries

n Range: https://github.com/rakudo/rakudo/blob/32902f25ca753860067a34eb9741aa5524dbe64e/src/core/Range.pm#L96 -- Aaron Sherman, M.: P: 617-440-4332 Google Talk, Email and Google Plus: a...@ajs.com Toolsmith, developer, gamer and life-long student.

Re: Justification for the "reversed" instruction format

I don't know Haskell, but isn't flip just: sub flip(&f) { -> $b, $a, |c { f($a, $b, |c) } } And then: perl6 -e 'sub flip(&f) { -> $a, $b, |c { f($b, $a, |c) } }; my &yas = flip &say; yas(1,2,3)' 213 Aaron Sherman, M.: P: 617-440-4332 Google Talk, Ema

Re: Justification for the "reversed" instruction format

Oh, and note that you can pass R'd reductions as if they were normal prefix ops: $ perl6 -e 'sub dueet(&op, *@list) { op @list }; say dueet &prefix:<[R-]>, 1..100' -4850 On Tue, Sep 6, 2016 at 12:51 PM, Aaron Sherman wrote: > > > $ perl6 -e 'my

Re: Justification for the "reversed" instruction format

$ perl6 -e 'my @numbers = 1..100; say [-] @numbers; say [R-] @numbers' -5048 -4850 In general, it's kind of pointless with bare infix ops, as you can just reverse the arguments, but when reducing or the like, it becomes much more valuable. On Tue, Sep 6, 2016 at 12:43 PM, Parrot Raiser <1parr..

Update for S32::Str and musings on sprintf

gs from: http://perldoc.perl.org/functions/sprintf.html Also, a review of the POSIX documentation might reveal additional items that should be documented: http://pubs.opengroup.org/onlinepubs/9699919799/functions/sprintf.html -- Aaron Sherman P: 617-440-4332 Google Talk: a...@ajs.com / aaronjsher...@gmail.com "Toolsmith" and developer. Player of games. Buyer of gadgets.

lol context and X

5) # hyper-. flattens? $ ../rakudo/perl6 -e '(1 .. 2 X 4 .. 5)>>.join(",").say' 14152425 Can someone explain why these all behave so differently, and why we chose to flatten so aggressively in so many cases, but not in some others? -- Aaron Sherman P: 617-440-4332 Google Talk: a...@ajs.com / aaronjsher...@gmail.com "Toolsmith" and developer. Player of games. Buyer of gadgets.

Return value of try

I was listening to the recent IO conversation on p6c, and decided to look at IO.pm in rakudo. I immediately saw a bit of code that worried me: try { ?$!PIO.close() } $! ?? fail($!) !! Bool::True Why is that so cumbersome? That seems like one of the most obvious

Re: threads?

On Thu, Oct 21, 2010 at 6:04 PM, Darren Duncan wrote: > Aaron Sherman wrote: > >> > Things that typically precipitate threading in an application: >> >> - Blocking IO >> - Event management (often as a crutch to avoid asynchronous code) >> - Legitim

Re: threads?

On Tue, Oct 12, 2010 at 10:22 AM, Damian Conway wrote: > Perhaps we need to think more Perlishly and reframe the entire question. > Not: "What threading model do we need?", but: "What kinds of non-sequential > programming tasks do we want to make easy...and how would we like to be > able to spec

Re: threads?

I've done quite a lot of concurrent programming over the past 23ish years, from the implementation of a parallelized version of CLIPS back in the late 80s to many C, Perl, and Python projects involving everything from shared memory to process pooling to every permutation of hard and soft thread man

Re: Buf.pm: FIFO and grammar

= 1 } ; my $a = 0; foo($a); say $a' 0 $ perl -le 'sub foo { $_[0] = 1 } my $a = 0; foo($a); print $a' 1 You might well be correct about how it's supposed to work, but that's certainly not the current behavior. On Fri, 2010-08-13 at 12:06 -0400, Aaron Sherman wrote

Re: Buf.pm: FIFO and grammar

; does not change the values passed in: sub foo(*...@_ is rw) { @_[0] = 1 } my $a = 0; foo($a); say $a; # 0 Kind of interesting that you can't easily emulate Perl 5's parameter passing... -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Buf.pm: FIFO and grammar

ation of the rules engine that could match either text or data, and that's a gigantic undertaking. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: pattern alternation (was Re: How are ...)

On Thu, Aug 5, 2010 at 2:43 PM, Tyler Curtis wrote: > On Thu, Aug 5, 2010 at 12:28 PM, Aaron Sherman wrote: > > While that's a nifty special case (I'm sure it will surprise me someday, > and > > I'll spend a half hour debugging before I remember this mail), i

Re: pattern alternation (was Re: How are ...)

On Thu, Aug 5, 2010 at 11:09 AM, Patrick R. Michaud wrote: > On Thu, Aug 05, 2010 at 10:27:50AM -0400, Aaron Sherman wrote: > > On Thu, Aug 5, 2010 at 7:55 AM, Carl Mäsak wrote: > > > I see this particular thinko a lot, though. Maybe some Perl 6 lint > > > tool or a

Re: pattern alternation (was Re: How are ...)

|<[a..z]>+/ for grins, :f[ull]l[ine] could use ^^ and $$. I suspect :full would almost always be associated with TOP, in fact. Boy am I tired of typing ^ and $ in TOP ;-) -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: How are unrecognized options to built-in pod block types treated?

across > all versions. :-( > If you never want documentation to break, then that's your only option. Someday we're going to decide to make an incompatible change to Perl's documentation system, and we'll have a very good reason to do so, I'd imagine. The right thing to do will be to make sure that we roll it out carefully and with all due warning. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: How are unrecognized options to built-in pod block types treated?

ad1 :image('foo.jpg') except for the fact that any unrecognized option of the first form is an error and any unrecognized option of the second form is allowed. That way, new features can be added to :reserved and migrated over time to stand-alone options after being listed in the release notes for a couple of cycles. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Smart match isn't on Bool

nt "when .foo == .bar" and I can't think of a good way to replace it, so I'll buy that it's worth making so many other obvious uses deprecated. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Natural Language and Perl 6

On Sun, Aug 1, 2010 at 6:46 AM, Timothy S. Nelson wrote: >Hi. I'm wondering if any thought has been given to natural language > processing with Perl 6 grammars. > > Yes. ;) -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Smart match isn't on Bool

, that's a bug, but imagine the poor maintenance programmer that tries to figure out what's going on. I feel for him/her. The only advantage he/she will have is that this is likely to be so common an error that they'll quickly learn to look for it first when smart-matching is involved :-/ -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Smart match isn't on Bool

On Sat, Jul 31, 2010 at 12:56 PM, David Green wrote: > > On 2010-07-30, at 4:57 pm, Aaron Sherman wrote: > >> given False { when True { say "True" } when False { Say "False" } > default { say "Dairy" } } > >> I don't think it'

Re: Suggested magic for "a" .. "b"

into some awful edge cases. Still, interesting stuff. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Smart match isn't on Bool

.new() === R.new()' Segmentation fault Clearly this is infinitely recursive, but one imagines it would be easy enough to put a maximum recursion depth on ===. I was about to say that === should check to see if X.WHICH eqv X, but I think that would slow things down too much. Setting a max recursion depth, on the other hand would be simple and fast. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Array membership test?

== True; Result: Rakudo exits silently with no newline So, the right way to search for value types in a list... is highly questionable right now. ;-) -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

just by knowing that the locale because they are finer grained (e.g. which Latin-using language does the word come from? What source language is most appropriate for the context? etc.) Maybe you throw an exception when you try to tell Perl that " TOPIXコンポジット1500構成銘柄" is a Japanese string

Re: Suggested magic for "a" .. "b"

On Wed, Jul 28, 2010 at 6:24 PM, Dave Whipp wrote: > Aaron Sherman wrote: > >> On Wed, Jul 28, 2010 at 11:34 AM, Dave Whipp >> wrote: >> >> To squint at this slightly, in the context that we already have 0...1e10 >>> as >>> a sequence gener

Re: Suggested magic for "a" .. "b"

On Wed, Jul 28, 2010 at 6:24 PM, Dave Whipp wrote: > Aaron Sherman wrote: > >> On Wed, Jul 28, 2010 at 11:34 AM, Dave Whipp >> wrote: >> >> To squint at this slightly, in the context that we already have 0...1e10 >>> as >>> a sequence gener

Re: Suggested magic for "a" .. "b"

ay initializers will involve "...". Why are we not calling that ".."? Just because we defined ".." first, and it grandfathered its way in the door? Because it resembles the math op? These don't seem like good reasons. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

Sorry I haven't responded for so long... much going on in my world. On Mon, Jul 26, 2010 at 11:35 AM, Nicholas Clark wrote: > On Tue, Jul 20, 2010 at 07:31:14PM -0400, Aaron Sherman wrote: > > > 2) We deny that a range whose LHS is "larger" than its RHS makes sen

Re: series operator issues

older > variables) includes any named parameters, You meant "named only" > then the index is used as > the argument corresponding to the first one. Named only... first... these terms are non-miscible, aren't they? I don't think named-only parameters have an ordering. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: series operator issues

lly from the previous n values as normal. That makes your examples: 0, { $^a + $^index } ... * 0, { $^a + (2 * $^index - 1) } ... * { $^index ** 2 } ... * 1, { $^a * $^index } ... * Not changing the syntax of closures seems like a reasonable goal at this late stage. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: series operator issues

I also think it's doable without a special tool: 0, { state $i = 1; $^a + $i++ } ... * That should work, no? Granted, state doesn't seem to work in Rakudo, unless I'm mis-understanding how to use it, but that's the idea. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

characters" which I'm defining as single codepoints which are neither combining nor modifying. If you like, we can have the conversation about what you do when you encounter combining and modifying codepoints, and I do think I agree with you largely, but I'd like to hold that for now. It's just too much of a rat-hole at this point. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

multi-character ranges

[changing the subject because it's now clear we have two different discussions on our hands. I think we're at or closing in on a consensus for "a" .. "z", and this discussion is "aa" .. "bb"] On Wed, Jul 21, 2010 at 1:56 AM, Darren Duncan wrote

Re: Suggested magic for "a" .. "b"

On Wed, Jul 21, 2010 at 1:28 AM, Aaron Sherman wrote: > > For reference, this is the relevant section of the spec: > > Character positions are incremented within their natural range for any > Unicode range that is deemed to represent the digits 0..9 or that is deemed > to be a

Re: Suggested magic for "a" .. "b"

OK, there's a lot here and my head is swimming, so let me re-consolidate and re-state (BTW: thanks Jon, you've really helped me understand, here). 1) The spec is somewhat vague, but the proposal that I made for single characters is not an unreasonable interpretation of what's there. Thus, we could

Re: Suggested magic for "a" .. "b"

ould avoid ever generating a combining or modifying codepoint in such a sequence (e.g. "Ѻ" ... "Ҋ" in Cyrillic which contains several combining characters for currency and counting as well as one undefined codepoint). -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

have around ranges that it doesn't think are legitimate for ranges: it repeats the LHS infinitely: "䷀" .. "䷿" - expected: all hexagram characters; got: first character, infinitely repeating. "鐀" .. "鐅" - expected: all CJK Unified Ideographs between u+9400 and u+9405; got: first character, infinitely repeating. "٠" .. "٩" - expected: all Arabic-Indic digits zero through nine; got: first digit (zero) repeating (note: bidi may confuse display in this email) "א" .. "ת" - expected: all Hebrew letters; got: first character (א) repeating (note: bidi may confuse display in this email) "Ａ" .. "Ｅ" - expected: all full width, capital letters A through E; got: full width A repeating. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

t;C" .. "A". Observe: $ ./perl6 -e 'say reverse("A" .. "C").perl' ["C", "B", "A"] $ ./perl6 -e 'say ("A" .. "C").perl' "A".."C" In order for reverse to work lazily, it woul

Re: Suggested magic for "a" .. "b"

ited, because the rules for any other sort of string that might make sense to a human are absurdly complex. As such, I think it suffices to say that, for the most part, ".." makes sense for single-character strings, and to expand from there, rather than trying to introduce anything more complex. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Suggested magic for "a" .. "b"

I like it. Though it does mean that the sequence generated > incrementing "Ab" repeatedly will diverge from "Ab" .. "Be" after 4 > iterations. > Also true, and I think that's a correct thing. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Suggested magic for "a" .. "b"

sequence does not increment (e.g. "AA", "AB" ... "ZZ") then there is an implication that counting is required. You should be able, in this case, to imply incrementing the left or right side as most significant (e.g. "AA", "BA" ... "ZZ" is also valid). It is, however, an error to try to increment indexes in any other ordering (e.g. "AAA", "ABA" ... "ZZZ"). Once a counting sequence has been established, lookahead must be employed to determine the extent of the range (e.g. "A", "B" can continue through all "Latin" Lu codepoints, so in order to know when to cycle, you must determine how many codepoints lie in the full range. This implies that length > 1 strings in "..." operations which imply a counting sequence, are not strictly evaluated lazily, though some laziness may still be employed. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: r31651 -[S13] try to make multisig semantics slightly more generic so sigs can do better pattern matching

r any parameter that occurs in > +multiple signatures with non-identical nominal types, the actual > +lexical variable will declared > "will *be* declared"? -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: S06 -- grammatical categories and macros

On Wed, Jun 30, 2010 at 7:33 PM, Jonathan Worthington wrote: > Aaron Sherman wrote: > >> See below for the S06 section I'm referring to. >> >> I'm wondering how we should be reading the description of user-defined >> operators. For example, "sub in

S06 -- grammatical categories and macros

y rules with a known prefix, by the longest-token-first rule.) Although the name of an operator can be installed into any package or lexical namespace, the syntactic effects of an operator declaration are always lexically scoped. Operators other than the standard ones should not be installed into the * namespace. Always use exportation to make non-standard syntax available to other scopes. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Filesystems and files [Was: Re: The obligation of free stuff: Google Storage]

gt; Yep, that makes perfect sense. Once I have a working VFS object that could be stored in there, that's probably the best way to go, unless someone proposes another way between now and then. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Perl 6 in non-English languages

I should point out that I've had a great deal of coffee. The technical details of what I've said are reasonable, but read the rest as off-the-cuff opinion. It's also true that seeing how Perl 6 would look/work when re-cast in the grammatical conventions of another human language would be very cool

Re: Perl 6 in non-English languages

uot;907 thousandsmallweights to the short ton" rather than "907 kilograms" and that's just not going to help anyone (yes, I'm aware that Brits try to spell that grammes, and I refer my right honorable limeys to ISO 8-1:2009). Sure, Perl 6 allows you to localize names. In theory, but I'd be very concerned about anyone who actually wanted to promote the use of such a thing. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: The obligation of free stuff: Google Storage

Franky, I don't think that it's something that SHOULD be answered prior to building the VFS layer itself, because that layer might dictate some design decisions, but my high level impulse is to say that open on a VFS token (be it a URI or some othe complex data) will yield a VFS-back-end spe

Re: r31337 -[S02] allow _ between radix and digits as suggested by ajs++

On Fri, Jun 18, 2010 at 10:26 PM, ajs wrote: > Attached, I've included test results, the tests and the patch (both to the > spectest suite and nqp-rx) to support this spec change. No... no I didn't. Here it is, attached as text. -- Aaron Sherman Email or GTalk: a...@ajs.com ht

Re: r31337 -[S02] allow _ between radix and digits as suggested by ajs++

> +    0x_bad_cafe > + >  =item * > >  The general radix form of a number involves prefixing with the radix > > -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

underscore in numbers

r $S10, rx184_tgt, $I11, 1 +ne $S10, "_", rx184_nodunder +add rx184_pos, 1 + rx184_nodunder: # rx subrule "decint" subtype=capture negate= rx184_cur."!cursor_pos"(rx184_pos) $P10 = rx184_cur."decint"() -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: The obligation of free stuff: Google Storage

On Wed, Jun 9, 2010 at 10:04 AM, Aaron Sherman wrote: > Has anyone begun to consider what kind of filesystem interface we want > for things like sftp, Amazon S3, Google Storage and other remote > storage possibilities? Is there any extant work out there, or should I > just start spit-

The obligation of free stuff: Google Storage

for things like sftp, Amazon S3, Google Storage and other remote storage possibilities? Is there any extant work out there, or should I just start spit-balling? -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: r31043 -[S32/Containers] Buf does Stringy, too

en considering this class's uses, brace style preferences notwithstanding. My knee-jerk response would be that this is fine the way it is now, but perhaps adding your suggestion as an alternative syntax could be considered for >6.0? Then again, no one cares what I say ;-) -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: r31050 -[S03] refine hyper dwimminess to be more like APL, with modular semantics

) ) ~~ (2,4,4,6) ) ok(( (1,2,3) »+» 1) ~~ (2,4,4,6) ) I tested these all with Rakudo, and they all currently fail, though I guess that's not shocking. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Advocating Perl 6

ually brief explanation every day. We'll see how long I can keep it up. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Parallelism and Concurrency was Re: Ideas for a"Object-Belongs-to-Thread" (nntp: message 4 of 20) threading model (nntp: message 20 of 20 -lastone!-)

27;s entirely (un)wise. Then again, it does simplify the world tremendously. I just wanted to get that all out there for thought. -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Fwd: URI replacement pseudocode

On Mon, May 17, 2010 at 3:34 PM, Moritz Lenz wrote: > > > Aaron Sherman wrote: > > > I had a hard time even getting basic code working like: > > > > token foo { blah } > > if "blah" ~~ m// { say "blah!" } > > > > (Se

Re: Fwd: URI replacement pseudocode

On Mon, May 17, 2010 at 3:34 PM, Moritz Lenz wrote: > > > Aaron Sherman wrote: > > > I had a hard time even getting basic code working like: > > > > token foo { blah } > > if "blah" ~~ m// { say "blah!" } > > > > (Se

Re: Perl6 and "accents"

he standard. The exegeses have no such status. Personally, I'd rather see them updated than thrown out, but I tried writing examples just for a few elements of S29 back in the day, and found the moving target to be too painful. Maybe Perl 6 has slowed down enough that it's more practical now? -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Fwd: URI replacement pseudocode

Ooops, took this off-list by accident. -- Forwarded message -- From: ajs Date: Mon, May 17, 2010 at 2:59 PM Subject: Re: URI replacement pseudocode To: Moritz Lenz Thank you for your responses! On Mon, May 17, 2010 at 1:37 PM, Moritz Lenz wrote: > Aaron Sherman wr

URI replacement pseudocode

.. \xDFFFD] + [\xE1000 .. \xEFFFD]> (from the IRI specification) -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: a more useful srand (was Re: r30369 - docs/Perl6/Spec/S32-setting-library)

uences are much-prized, and any language that starts off with some poor assumptions will ultimately pay for it. Some good reading for recent work: http://www.math.sci.hiroshima-u.ac.jp/~m-mat/MT/SFMT/ http://eprint.iacr.org/2006/086 http://lcamtuf.coredump.cx/oldtcp/tcpseq.html http://www.avatar.se/p

Re: underscores vs hyphens (was Re: A new era for Temporal)

s not, but certainly they should at least yield warnings by default. PS: While I never finished the implementation of Sand, its simplistic guide to Unicode identifiers might be useful in illuminating what I'm describing above: http://www.ajs.com/ajswiki/Sand:_Syntax_and_Structure#Identifiers -- Aaron Sherman Email or GTalk: a...@ajs.com http://www.ajs.com/~ajs

Re: Parsing data

On Thu, Oct 8, 2009 at 12:57 AM, David Green wrote: > I agree that being able to parse data structure would be *extremely* useful. >  (I think I posted a suggestion like that at one time, though I didn't > propose any syntax.)  There is already a way to parse data -- Signatures, > but not with th

Re: Parsing data

Sorry, I accidentally took the thread off-list. Re-posting some of my comments below: On Wed, Oct 7, 2009 at 6:50 PM, Moritz Lenz wrote: > Aaron Sherman wrote: >> One of the first things that's becoming obvious to me in playing with >> Rakudo's rules is that parsing stri

Parsing data

One of the first things that's becoming obvious to me in playing with Rakudo's rules is that parsing strings isn't always what I'm going to want to do. The most common example of wanting to parse data that's not in string form is the YACC scenario where you want to have a function produce a stream

Re: [perl #69194] rakudo 2009-08 and when with lists

On Sat, Sep 19, 2009 at 9:45 PM, David Green wrote: > On 2009-Sep-19, at 5:53 am, Solomon Foster wrote: > > The one thing that worries me about this is how :by fits into it all. >>rakudo: given 1.5 { when 1..2 { say 'between one and two' }; say >> 'not'; }; >>rakudo: given 1.5 {

Re: [perl #69194] rakudo 2009-08 and when with lists

Redirecting thread to language because I do agree that this is no longer a matter of a bug. On Fri, Sep 18, 2009 at 9:28 AM, Moritz Lenz via RT < perl6-bugs-follo...@perl.org> wrote: > On Thu Sep 17 08:53:59 2009, ajs wrote: > > This code behaves as expected, matching 2 or 3 in only one out of th

POD classes -- a suggestion

I'd really like to be able to assign a class to POD documentation. Here's an example of why: class Widget is Bauble #= A widget is a kind of bauble that can do stuff { has $.things; #= a collection of other stuff #==XXX{ This variable needs to be replaced for political reasons }

Re: S26 - The Next Generation

I'm jumping in on an old conversation because I only just had time to catch up last night. I have a few questions that I think are probably still pertinent. On Sun, Aug 16, 2009 at 4:26 PM, Damian Conway wrote: > > Executive summary: > > * Pod is now just a set of specialized forms of Perl 6

Re: Testing Perl 6 analog to Perl 5's tie.

On Sun, Aug 2, 2009 at 1:10 PM, Moritz Lenz wrote: > Let's pick up this old mail before it gets completely warnocked ;-) > > For the record, this discussion only applies to scalar implementation > types. For example for Arrays I expect things to work by overriding the > method postcircumfix:<[ ]>

Fwd: Re-thinking file test operations

Sorry, I sent this just to Mark. Wasn't my intention. -- Forwarded message -- From: Aaron Sherman Date: Fri, Jul 10, 2009 at 6:58 PM Subject: Re: Re-thinking file test operations To: "Mark J. Reed" On Fri, Jul 10, 2009 at 5:31 PM, Mark J. Reed wrote: >

Re: Re-thinking file test operations

On Thu, Jul 9, 2009 at 6:22 PM, Moritz Lenz wrote: > > $str.File.e # same, different names Brainstorming a bit here Str is a class that describes collections of characters (among some other typographical constructs, yadda, yadda, Unicode, yadda). There is a commonly used speci

Re: Huffman's Log: svndate r27485

On Fri, Jul 10, 2009 at 3:32 PM, Mark J. Reed wrote: > The clash between 'log' for 'logarithm' and 'log' for 'write to log > file' is unfortunate, but since you have to define logging parameters > somewhere anyway, I'm OK with having to call that sort of log as a > method on a logger object inst

Re: Runtime role issues

Ovid wrote: The "intermediate class" solves the problem but it instantly suggests that we have a new "design pattern" we have to remember. Basically, if I can't lexically scope the additional behavior a role offers, I potentially need to remove the role or use the "intermediate class" pattern.

P5's s[pat][repl] syntax is dead

@larry[0] wrote: Log: P5's s[pat][repl] syntax is dead, now use s[pat] = "repl" Wow, I really missed this one! That's a pretty big thing to get my head around. Are embedded closures in the string handled correctly so that: s:g[\W] = qq{\\{$/}}; Will do what I seem to be expecting i

Capturing subexpression numbering example

The example in S05 under "Subpattern numbering" isn't quite complex enough to give the reader a full understanding of the ramifications of the re-numbering that occurs with alternations, especially with respect to the combination of capturing and non-capturing subpatterns. I've written a small

Updated: Re: Hash composers and code blocks

Aaron Sherman wrote: (updated based on followup conversations) Proposal: A sigil followed by [...] is always a composer for that type. %[...]- Hash. @[...]- Array. &[...]- Code. |[...]- Capture. Identical to \(...). $[...]- Scalar. Like item(...),

Re: Hash composers and code blocks

Mark J. Reed wrote: On 10/5/06, Aaron Sherman <[EMAIL PROTECTED]> wrote: Proposal: A sigil followed by [...] is always a composer for that type. %[...] - Hash. Unicode: ⦃...⦄ @[...] - Array. Unicode: [...] ? - Seq. Unicode: ⎣...⎤ &[...] - Cod

Re: Hash composers and code blocks

Aaron Sherman wrote: Proposal: A sigil followed by [...] is always a composer for that type. %[...]- Hash. Unicode: ⦃...⦄ @[...]- Array. Unicode: [...] ... I left out ::, which is probably a mistake. Part of the elegance of this, IMHO, is that it behaves the same for all

Re: import collisions

Jonathan Lang wrote: What if I import two modules, both of which export a 'foo' method? That's always fine unless they have exactly the same signature. In general, that's not going to happen because the first parameter is created from the invocant. Thus: use HTML4; use Math:

Hash composers and code blocks

S04 now reads: == However, a hash composer may never occur at the end of a line. If the parser sees anything that looks like a hash composer at the end of the line, it fails with "closing hash curly may not terminate line" or some such. my $hash = { 1 => { 2 => 3, 4 => 5 },

Re: "Don't tell me what I can't do!"

Trey Harris wrote: I read it as "yes, you *can* put strictures on the using code into a library, though I wouldn't do it and would say that any module that does so shouldn't be released on CPAN for general use. ..." Hey, I have an idea. Let's write a module that enforces that! Seriously, I t

Mailing list archive and index

I'm noodling around with the idea of creating an archive and index of all of the messages to the mailing list over the years for purposes of quickly finding all of the messages that have definitive information on a given topic. Simply searching on Google or through my mail spool just doesn't cu

Re: Exceptions on hypers

Aaron Sherman wrote: Damian Conway wrote: @bar».foo if $baz; That brought to mind the question that I've had for some time: how are exceptions going to work on hyper-operators? Will they kill the hyperoperation in-progress? e.g. what will $i be: Corrected example follows (there

Exceptions on hypers

Damian Conway wrote: @bar».foo if $baz; That brought to mind the question that I've had for some time: how are exceptions going to work on hyper-operators? Will they kill the hyperoperation in-progress? e.g. what will $i be: my $i = 0; class A { method inci() { die if $i

Re: Nested statement modifiers.

Paul Seamons wrote: It relates to some old problems in the early part of the RFC/Apocalypse process, and the fact that: say $_ for 1..10 for 1..10 Was ambiguous. The bottom line was that you needed to define your parameter name for that to work, and defining a parameter name on a modifi

  1   2   3   4   5   6   >