Re: Bag / Set ideas - making them substitutable for Arrays makes them more useful

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/7/10 23:19 , Jon Lang wrote: > 1 -- 2 -- 3 > > Would be a Bag containing three elements: 1, 2, and 3. > > Personally, I wouldn't put a high priority on this; for my purposes, > >Bag(1, 2, 3) > > works just fine. Hm. Bag as [! 1, 2, 3

Re: Tweaking junctions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/22/10 13:00 , Dave Whipp wrote: > Damian Conway wrote: >> I've been thinking about junctions, and I believe we may need a small >> tweak to (at least) the jargon in one part of the specification. > > When this issue has been raised in the past,

Re: Ruby Fibers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/15/10 10:22 , B. Estrade wrote: > Pardon my ignorance, but are continuations the same thing as > co-routines, or is it more primitive than that? Also, doesn't this > really just allow context switching outside of the knowledge of a > kernel thre

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/1/10 00:31 , Brandon S Allbery KF8NH wrote: > As for serializeability, I think .perl is being used for two different > things and we need to separate them. If it's there for debugging, you want Addendum, since as I reread my message

Re: [perl6/specs] 58fe2d: [S12] spec setting and getting values of attribute...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/30/10 16:46 , Moritz Lenz wrote: > 1) please don't abuse MONKEY_TYPING for anything that might look like > dangerous If Perl 6 is still Perl then in some sense it implies that "dangerous" is accepted practice. :) That said... > 2) I find .perl

Re: [perl6/specs] 761178: remove some some duplicate words words

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/8/10 14:24 , Patrick R. Michaud wrote: > On Wed, Sep 08, 2010 at 04:02:10PM +0400, Richard Hainsworth wrote: >> I do want the diffs back: its the only way I have to keep at least >> some idea of what is changing any why. > > We know that a lot of

Re: [perl6/specs] 761178: remove some some duplicate words words

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/7/10 08:17 , nore...@github.com wrote: > Commit: 7611788411e5aff5f3ae150e2da9929ee546d6d8 > > http://github.com/perl6/specs/commit/7611788411e5aff5f3ae150e2da9929ee546d6d8 It was nicer when these contained the actual diffs like they used to,

Re: Buf.pm: FIFO and grammar

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/13/10 22:03 , Aaron Sherman wrote: > On Fri, Aug 13, 2010 at 8:11 PM, Jon Murray wrote: > >> My understanding from synopses was that you get the Perl 5 behaviour if >> you omit the signature on your function declaration (though I >> unfortunatel

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 8/4/10 21:26 , Darren Duncan wrote: > jerry gay wrote: >> are there codepoints in unicode that may be either upper-case or >> lower-case, depending on the charset? if so, then there's ambiguity >> here, depending on the user's locale. i suspect no

Re: Unwanted warnings (was Re: Something wrong with str.reverse)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 23:26 , David Green wrote: > On 2010-06-18, at 10:48 am, Larry Wall wrote: >>0123; # warns >>0123; # ok! # suppresses this warning here >>0123; # OK! # suppresses this warning from now on >

Re: Breaking encapsulation by detaching a private-variable-accessing method from one object and calling it on another

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 14:38 , Stefan O'Rear wrote: > On Sat, Jul 31, 2010 at 02:36:02PM -0400, Brandon S Allbery KF8NH wrote: >> The whole concept of detaching and attaching methods seems suspect to me; in >> particular, attaching a met

Re: Breaking encapsulation by detaching a private-variable-accessing method from one object and calling it on another

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 14:23 , Carl Mäsak wrote: > a. Allow this form of encapsulation breakage. > b. Disallow detaching of certain methods. > c. Disallow attaching of certain anonymous methods. > > I must confess I don't particularly like either option. I'm by n

Re: Smart match isn't on Bool

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 12:56 , David Green wrote: > a boolean IS useful. The fact that this question keeps coming up, > even on the p6l list, seems to demonstrate that the "helpful" way > isn't completely natural or obvious (at least, not to everyone). Thank you;

Re: Smart match isn't on Bool

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 11:17 , Mark J. Reed wrote: > What if you say 'when test($_)'? Or just 'when &test'? How do you > smart match on a function: call the func with the target as argument > and use the return value, or call it without any argument and compare

Re: Smart match isn't on Bool

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/31/10 03:33 , Moritz Lenz wrote: > In this code: > > sub test() { True }; > > given 0 { > when test() { say "OH NOEZ" } > } > > I don't think it's unreasonable to expect the output to be "OH NOEZ". I think there's a confusion about what gi

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/29/10 08:15 , Leon Timmermans wrote: > On Thu, Jul 29, 2010 at 3:24 AM, Darren Duncan > wrote: >> $foo ~~ $a..$b :QuuxNationality # just affects this one test > > I like that > >> $bar = 'hello' :QuuxNationality # applies anywhere the Str

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

On 7/28/10 8:07 PM, Michael Zedeler wrote: > On 2010-07-29 01:39, Jon Lang wrote: >> Aaron Sherman wrote: In smart-match context, "a".."b" includes "aardvark". >>> No one has yet explained to me why that makes sense. The continued >>> use of >>> ASCII examples, of course, doesn't help. Does "

Re: series operator issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/22/10 11:18 , Jon Lang wrote: > Second, I'm trying to think of a simple and intuitive way to write up > a series expression for: > >triangle numbers: 0, 1, 3, 6, 10, 15, 21, etc. >square numbers: 0, 1, 4, 9, 16, 25, 36, etc. >factoria

Re: r31696 -[S32/Temporal] Permit day-of-month on Dates.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/15/10 12:21 , Mark J. Reed wrote: > By analogy, I'd say week-of-year should work as well. Wasn't the week stuff punted to a non-core module because there are too many differences in how it's handled (week starts on Sunday in the US and Israel and

Re: The obligation of free stuff: Google Storage

On Jun 10, 2010, at 07:22 , Leon Timmermans wrote: I agree it should be similar to normal FS interactoin to make matters as intuitive as possible, but I horrified by the idea of overloading open() that way. That's a PHP mistake I wouldn't like seeing repeated. If you want open to do something tha

Re: Proposal for a new Temporal time-measurement paradigm

Minor nit: On Apr 21, 2010, at 04:57 , Richard Hainsworth wrote: If a calendar system, eg., Chinese, Muslim and Jewish, defines days in the same way, eg., starting at midnight and incorporating leap seconds, for a time-zone, then the naming of the days is done by The Jewish, Muslim, and Bah

Re: A common and useful thing that doesn't appear to be easy in Perl 6

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 7, 2010, at 00:52 , Larry Wall wrote: more syntactic and/or semantic sugar. It's just a bit awkward, after you say: enum Permissions ; subset Perms of Set of Permissions; that the name of the single-member sets are Perms(Read) Pe

Re: You never have privacy from your children in Perl 6

On Mar 27, 2010, at 15:43 , Darren Duncan wrote: My own take on 'trusts' is that I consider its main purpose is to let programmers *avoid* contrivances when they want to define something that would otherwise be a single class but is split into multiple classes for better elegance. For examp

Re: r29976 - docs/Perl6/Spec

On Mar 9, 2010, at 18:10 , Timothy S. Nelson wrote: Algol 68 is notorious as a failure. Let's hope things are different here. As a programming language, it was a failure, in large part because it was a bit too forward-looking for the available compiler technology. (It's still a bit tou

Re: r29976 - docs/Perl6/Spec

On Mar 8, 2010, at 11:04 , Carl Mäsak wrote: commitbot (), Brandon (>>>), Mark (>>), Carl (>): +has $!age is ref; # BUILD will automatically use ref binding, not copy Perl6 isn't done until it has reinvented Algol 68? [...] I'm not sure what exactly the repercussions of doing att

Re: r29976 - docs/Perl6/Spec

On Mar 8, 2010, at 06:23 , Carl Mäsak wrote: commitbot (>), Brandon (>>): +has $!age is ref; # BUILD will automatically use ref binding, not copy Perl6 isn't done until it has reinvented Algol 68? Unaware of what Algol 68 represents in programming language history, I perused Wikipedia

Re: r29976 - docs/Perl6/Spec

On Mar 7, 2010, at 09:42 , pugs-comm...@feather.perl6.nl wrote: +has $!age is ref; # BUILD will automatically use ref binding, not copy Perl6 isn't done until it has reinvented Algol 68? -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [o

Re: Temporal seems a bit wibbly-wobbly

(re subject: does it go `Ding!' when there's Stuff?) On Feb 20, 2010, at 00:30 , Larry Wall wrote: but an astronomer? But no, many millions of computers have to accommodate to the convenience of a very few people. And most computers still don't know how to do even that accommodation, sinc

Re: r29768 - docs/Perl6/Spec

On Feb 17, 2010, at 17:18 , Smylers wrote: pugs-comm...@feather.perl6.nl writes: Author: lwall +++ docs/Perl6/Spec/S02-bits.pod2010-02-17 19:15:34 UTC (rev 29768) +rhyme((1,2),3,:mice) # rhyme has 2 arguments Should that say 3 arguments? (If not, please can somebody clarify w

Re: Gripes about Pod6 (S26)

On Feb 12, 2010, at 19:57 , Timothy S. Nelson wrote: On Wed, 10 Feb 2010, Jon Lang wrote: John Gabriele wrote: Personally, I've always thought that Perl has a very natural feel to it, and deserves a doc markup format that's also natural: [Markdown] (and [Pandoc]'s Markdown has just the right ad

Re: r29540 - docs/Perl6/Spec

On Jan 16, 2010, at 01:47 , pugs-comm...@feather.perl6.nl wrote: -=head1 Regexes are now first-class language, not strings +=head1 Regexes are now a first-class language, not strings I'm not sure if that's the correct reading, or "...now first-class language [elements]". Or possibly using "

Re: Comments on S32/Numeric#Complex

On Dec 16, 2009, at 19:46 , Dave Whipp wrote: yary wrote: At 00:15 +0100 12/17/09, Moritz Lenz wrote: Not quite, .abs returns one of the polar coordinates (the magnitude), so only a method is missing that returns the angle. Any ideas for a good name? Would a method called "phi" with a unicod

Re: r28751 - docs/Perl6/Spec

On Oct 11, 2009, at 06:36 , Mark J. Reed wrote: That's not grammatical; you've just created a run-on sentence. Why not leave it as a colon? Or semicolon. I agree comma seems wrong. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,hei

Re: Synopsis 02: Range objects

On Aug 27, 2009, at 17:48 , Jon Lang wrote: On Thu, Aug 27, 2009 at 2:36 PM, Mark J. Reed wrote: I think $a <= $^x <= $b is short enough, and lets you choose between < and <= on both ends and without having to remember how many dots each maps to. "How many dots"? .. vs. ... operators, I p

Re: S26 - The Next Generation

On Aug 17, 2009, at 14:34 , raiph mellor wrote: However it seems we have to pay a price: each act of rendering a Pod file actually means executing the program that's being documented (at least the BEGIN blocks and other stuff that happens at compile time), with all the security risks implied. So

Re: S26 - The Next Generation

On Aug 17, 2009, at 14:27 , Moritz Lenz wrote: ll 99: followed by a valid identifierN< A valid identifier is a sequence of alphanumerics and/or underscores, beginning with an alphabetic or underscore Is there a good reason to deviate from Perl 6's definition of an identifier?

Re: Filename literals

On Aug 14, 2009, at 16:17 , Mark J. Reed wrote: On Fri, Aug 14, 2009 at 3:35 PM, Darren Duncan wrote: Under Mac OS X, all drives, root or otherwise, are accessible under '/Volumes//...', and Unix in general lets you mount drives anywhere. I imagine Windows supports more ways of denoting driv

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

On Aug 2, 2009, at 13:10 , Moritz Lenz wrote: Kyle Hasselbacher wrote: My patchwork readings lead me to believe I could test Perl 6's tie-like feature with something like the below code, which I don't expect to even compile, what with '???' in places. My question is: am I on the right track? O

Re: Reusing code: "Everything but the kitchen sink"

On Jul 12, 2009, at 20:15 , David Green wrote: sub nighttime (Canine $rover) { $rover.bark if any(burglars()); } (...) 3) $rover acts like a Canine, but the rest of the original $dogwood arg (the Tree parts) are still there; they just aren't used unless somehow explicitly brought out; for

Re: Re-thinking file test operations

On Jul 9, 2009, at 18:22 , Moritz Lenz wrote: Somehow the current file test syntax, 'filename' ~~ :e, looks like a not well-though-out translation of Perl 5's syntax, -e 'filename'. That would be because it is; originally the filetests were perl5- style, but pugs refused to parse them becaus

Re: YAPC::EU and Perl 6 Roles

On Jul 7, 2009, at 08:13 , Jonathan Worthington wrote: Brandon S. Allbery KF8NH wrote: I was trying to figure out how to do it with nextsame, but that's not looking very simple. On the other hand, if they were multis then they get added to the multi candidate list and therefore yo

Re: YAPC::EU and Perl 6 Roles

On Jul 7, 2009, at 07:34 , Jonathan Worthington wrote: Jon Lang wrote: I believe that the official word is to say: class PracticalJoke does Bomb does Spouse { method fuse () { Bomb::fuse } method explode () { Spouse::explode } } This way won't work, because: * It's doing a sub call t

Re: XOR does not work that way.

On Jun 22, 2009, at 19:12 , Minimiscience wrote: On Jun 22, 2009, at 5:51 PM, Damian Conway wrote: Perl 6's approach to xor is consistent with the linguistic sense of 'xor' ("You may have a soup (x)or a salad (x)or a cocktail"), and also with the IEEE 91 standard for logic gates. I don't th

Re: renaming or adding some operators

On May 30, 2009, at 15:38 , Larry Wall wrote: Perhaps something like use *; should pull in all the Unicode operators. Which if course means that any golfing would start with *; ⨷ perhaps? It only makes sense that a Unicode operator be used to pull in all of Unicode. -- brandon s

Re: renaming or adding some operators

On May 29, 2009, at 22:33 , Jon Lang wrote: "also" is an ordered, short-circuiting version of "&" (and thus "all"). For some time now, I've wanted an analog for '|' and 'any' - but the only name I can think of for it would be 'else', which has some obvious clarity issues. I have seen "x (alt.

Re: Amazing Perl 6

On May 29, 2009, at 22:40 , Timothy S. Nelson wrote: On Fri, 29 May 2009, John M. Dlugosz wrote: Ah yes, on the PC historically you hold down the ALT key and type the code with the numpad keys. At least when I used it, this was a decimal, rather than hex number, and had to be preceded by a

Re: Amazing Perl 6

On May 29, 2009, at 21:50 , Timothy S. Nelson wrote: some Linux programs support it too. Unfortunately my e-mail program (Pine) seems to have some trouble with unicode -- I may have to look at alternatives after 14 years of use :(. http://www.washington.edu/alpine/ -- brandon s. allbery [

Re: Amazing Perl 6

On May 29, 2009, at 15:43 , John M. Dlugosz wrote: Care to try ☃ ? That's alt-meta-hyper-doublebucky-cokebottle. *puzzled as to why OSX Character Map thinks that's related to 雪* -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimdal,

Re: Amazing Perl 6

On May 28, 2009, at 06:43 , Jon Lang wrote: What I'm wondering is how the list knows to feed two items into '[+]'. While 'infix:<+>' must accept exactly two arguments, '[+]' can accept an arbitrarily long (or short) list of arguments. I thought that at first too, then remembered a discussion a

Re: Amazing Perl 6

On May 27, 2009, at 18:05 , John M. Dlugosz wrote: And APL calls it "|¨" (two little dots high up) buh? Metaoperator / (+/LIST). -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimdal,too many hats] allb...@ece.cmu.edu electrical and

Re: Amazing Perl 6

On May 27, 2009, at 15:42 , Daniel Carrera wrote: Mark J. Reed wrote: Note that of the examples given, only Perl 6 and Common Lisp do two things that help immensely simplify the result: 1. reference the built-in * operator directly, without having to wrap it in a lambda expression; 2. actua

Re: Amazing Perl 6

On May 27, 2009, at 13:59 , Daniel Carrera wrote: Wow... That's a foldl! In a functional language, that would be called a fold. It's very popular in Haskell. I like that Perl 6 seems to be taking steps in the direction of functional languages. First lazy lists (0..Inf) and now a fold. :-D

Re: Illustration of stuff we've been discussing

On May 28, 2009, at 10:27 , John M. Dlugosz wrote: Daniel Ruoso daniel-at-ruoso.com |Perl 6| wrote: Em Qui, 2009-05-28 às 00:24 -0500, John M. Dlugosz escreveu: Please see and talk to me about it. The illustratino is cool, but it doesn't

Re: "Unicode in 'NFG' formation" ?

On May 18, 2009, at 21:54 , Larry Wall wrote: On Mon, May 18, 2009 at 07:59:31PM -0500, John M. Dlugosz wrote: No, a few million code points in the Unicode standard can produce an arbitrary number of unique grapheme clusters, since you can apply as many modifiers as you like to each different ba

Re: "Unicode in 'NFG' formation" ?

On May 18, 2009, at 14:16 , Larry Wall wrote: On Mon, May 18, 2009 at 11:11:32AM +0200, Helmut Wollmersdorfer wrote: 3) Details of 'life-time', round-trip. Which is a very interesting topic, with connections to type theory, scope/domain management, and security issues (such as the possibility

Re: "Unicode in 'NFG' formation" ?

On May 18, 2009, at 09:21 , Mark J. Reed wrote: If you're doing arithmetic with the code points or scalar values of characters, then the specific numbers would seem to matter. I'm I would argue that if you are working with a grapheme cluster ("grapheme"), arithmetic on individual grapheme v

Re: Getting rid of want()

On 2009 Mar 31, at 17:04, Moritz Lenz wrote: We had a discussion on #perl6 tonight about how to implement want(), and basically came to no conclusion. Then I came up with the idea that any lazy implementor will come up with: drop it from the language. Hm, I was under the impression that want(

Re: $?OS change

On 2009 Mar 2, at 6:19, Timothy S. Nelson wrote: On Mon, 2 Mar 2009, Chris Dolan wrote: On Mar 2, 2009, at 12:04 AM, Timothy S. Nelson wrote: Hi. I note that we have $?OS, $?VM, and $?DISTRO (and their $* counterparts). I'd like to recommend that we eliminate $?OS, and replace it with $?K

Re: Comparing inexact values (was "Re: Temporal changes")

On Feb 26, 2009, at 14:27 , Jon Lang wrote: Jon Lang wrote: Brandon S. Allbery wrote: Jon Lang wrote: I'm not sold on the notion that Num should represent a range of values Arguably a range is the only sane meaning of a floating point number. Perhaps; but a Num is not necessarily a floatin

Re: Comparing inexact values (was "Re: Temporal changes")

On 2009 Feb 26, at 13:00, Jon Lang wrote: I'm not sold on the notion that Num should represent a range of values Arguably a range is the only sane meaning of a floating point number. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] allb...@kf8nh.com system administrator [openafs,heimd

Re: Temporal changes

On 2009 Feb 23, at 8:34, Ruud H.G. van Tol wrote: Martin D Kealey wrote: Ah, we want a noun that isn't readily confused as an adjective. Suitable terms might include: Instant Jiffy Juncture Moment Occasion Snap Tick ... Once :) "Then"? -- brandon s. allbery [solaris,freebsd,perl,pugs,hask

Re: r25490 - docs/Perl6/Spec

On 2009 Feb 23, at 22:43, Timothy S. Nelson wrote: On Mon, 23 Feb 2009, jason switzer wrote: On Sun, Feb 22, 2009 at 9:47 PM, wrote: +$*PROGRAM_NAME # name of the program being executed How does this differ from $*EXECUTABLE_NAME? Good question. Anyone? I would assume $*PRO

Re: r25490 - docs/Perl6/Spec

On 2009 Feb 22, at 22:47, pugs-comm...@feather.perl6.nl wrote: +$?PUGS_VERSION # Pugs version (not canonical) +$*PUGS_HAS_HSPLUGINS # True if Pugs was compiled with support for hsplugins + # (not canonical) These should not be part of the standard. But while

Re: Perl's internal time (was: Re: r25445 - docs/Perl6/Spec/S32-setting-library)

On 2009 Feb 20, at 14:36, Chris Dolan wrote: UTC: TAI with an offset, as corrected for the actual revolution of the Earth: usually 60 seconds in a minute, but occasionally 59 or 61. 60 minutes in every hour (so 3599, 3600, or 3601 seconds), 24 hours in every day (86399, 86400, or 86401 seconds

Re: r25445 - docs/Perl6/Spec/S32-setting-library

On 2009 Feb 20, at 12:21, Daniel Ruoso wrote: Em Sex, 2009-02-20 às 10:40 -0600, Dave Rolsky escreveu: On Fri, 20 Feb 2009, Daniel Ruoso wrote: If we're going to use an epoch, it should be the Operating System's epoch. Anything else will lead to confusion and disorder ;P And which OS epoch wou

Re: Exegesis 7/format() question

On 2009 Feb 17, at 1:54, Timothy S. Nelson wrote: Hi all. According to S29, the Perl 5 format() function is obsolete, and it says "See Exegesis 7". According to Exegesis 7, there will be a Form.pm which implements similar functionality, but has to be "use"d. My questions are: 1. Is

Re: The use of roles in S16 (Was: Re: r25328 - docs/Perl6/Spec)

On 2009 Feb 16, at 22:44, Timothy S. Nelson wrote: So you can have a stream handle which does IO::Writeable, but will throw an error on any attempt to write? Anyway, you've answered my question in the other e-mail. Not sure what you're getting at, but the obvious example is a writeable h

Re: r25328 - docs/Perl6/Spec

On 2009 Feb 15, at 22:50, Timothy S. Nelson wrote: On Sat, 14 Feb 2009, Leon Timmermans wrote: +=item sysopen I vote for sysopen (and all other sys functions) to be wiped out of existence. Disagree -- I think these belong in IO::Unbuffered. Maybe we could make that optional, though I

Re: r25328 - docs/Perl6/Spec

On 2009 Feb 14, at 12:01, Leon Timmermans wrote an unending refrain of: Why should this do POSIX? What about non-POSIX operating systems? I think the point here is that on POSIX systems that gets you ioctl() and fcntl(), and on non-POSIX systems either they don't exist or they throw runtim

Re: r25182 - docs/Perl6/Spec

On 2009 Feb 6, at 6:24, Daniel Ruoso wrote: Em Sex, 2009-02-06 às 02:07 -0500, Brandon S. Allbery KF8NH escreveu: I would think fcntl() is just the Unix version of a more general concept, which is probably wider than POSIX. Maybe this wider concepts can be expressed in their own roles, as

Re: r25200 - docs/Perl6/Spec t/spec

On 2009 Feb 5, at 13:51, Larry Wall wrote: Pity that -F specifies the ground. Hey, I know, let's make -G the figure, that makes about as much sense as -x vs +x, or electrons vs positrons... :) Someone's been rereading _Gödel,_Escher,_Bach_? -- brandon s. allbery [solaris,freebsd,perl,pugs,h

Re: r25182 - docs/Perl6/Spec

On 2009 Feb 4, at 12:56, Leon Timmermans wrote: On Wed, Feb 4, 2009 at 4:37 PM, wrote: +=item method IO dup() Do we really want that? POSIX' dup does something different from what many will expect. In particular, the new file descriptors share the offset, which can result in some really con

Re: r25182 - docs/Perl6/Spec

On 2009 Feb 4, at 11:45, Aaron Crane wrote: FWIW, I prefer the traditional spelling, "writable". Google suggests that "writeable" is more common on the web, though; 4.8 versus 3.7 Mghits. I have to admit that "writable" suggests to me that you can serve a writ on it; an unlikely case for eve

Re: r25102 - docs/Perl6/Spec

On 2009 Jan 30, at 11:30, Larry Wall wrote: So I'm open to suggestions for what we ought to call that envelope if we don't call it the prelude or the perlude. Locale is bad, environs is bad, context is bad...the wrapper? But we have dynamic wrappers already, so that's bad. Maybe the setting, l

Re: RFD: Built-in testing

On 2009 Jan 21, at 7:35, Carl Mäsak wrote: Moritz (>): So Larry and Patrick developed the idea of creating an adverb on the test operator instead: $x == 1e5 :ok('the :ok makes this is a test'); I'm trying to explain to myself why I don't like this idea at all. I'm only partially successfu

Re: [PATCH] Add .trim method

On 2009 Jan 12, at 15:17, Ovid wrote: " בָּרוּךְ שֵׁם כְּבוֹד מַלְכוּתוֹ לְעוֹלָם וָעֶד." If you can't see that in your client, that's Hebrew from http://www.i18nguy.com/unicode/shma.html and means "Hear O Israel, the Lord is our God, the Lord is One". Actually that's the res

Re: r24769 - docs/Perl6/Spec

On 2009 Jan 5, at 11:54, pugs-comm...@feather.perl6.nl wrote: + our Str multi method perl (Object $o) + +Returns a perlish representation of the object, so that calling C +on the returned string reproduces the object as good as possible. My inner English teacher cringes in pain. It should b

Re: "use" semantics

On 2009 Jan 4, at 8:53, Carl Mäsak wrote: Now, I can precompile the B module to PIR without a problem, but when I compile the A module, Rakudo/Parrot aborts because it runs the code in B and dies. $ parrot languages/perl6/perl6.pbc --target=pir --output=B.pir B.pm $ parrot languages/perl6/perl6

Re: Recommended Perl 6 best practices?

On 2008 Dec 20, at 13:39, Carl Mäsak wrote: Maybe this counts as a best practice, or maybe it's more of a "pattern". In a recent piece of code, I found a way to exploit code blocks to act like "return statements with side effects". The resulting code became very clean, so I decided to blog about

Re: 6PAN idea

On 2008 Dec 16, at 23:00, Timothy S. Nelson wrote: One thing I've been working on recently is a (Perl 5) object that models package metadata. In theory, it should be able to model the metadata from a .rpm, a .deb, a CPAN package, or whatever. Then you read the data using a "metadata input

Re: Roles and IO?

On 2008 Dec 11, at 20:16, Leon Timmermans wrote: One main problem with filehandles is that are rather diverse. The only operation that all of them have in common is close. Reading versus Be glad Xenix is dead. There were filehandles which didn't even support close() (they were actually handl

Re: Files, Directories, Resources, Operating Systems

On 2008 Dec 9, at 21:11, Charles Bailey wrote: It may well be that a fine-grained interface isn't practical, but perhaps there are some basics that we could implement, such as - set owner of this thing - (maybe) set group of this thing Group is problematic; I don't recall Windows having group

Re: Files, Directories, Resources, Operating Systems

On 2008 Dec 9, at 19:56, Aristotle Pagaltzis wrote: * Aristotle Pagaltzis <[EMAIL PROTECTED]> [2008-12-10 01:10]: Well go on. Btw, I just realised that it can be read as sarcastic, which I didn’t intend. I am honestly curious, even if skeptical. I am biased, but I am open to be convinced. B

Re: S16: chown, chmod

On 2008 Nov 24, at 10:45, dpuu wrote: PS. From S16, q{ ... On POSIX systems, you can detect this condition this way: use POSIX qw(sysconf _PC_CHOWN_RESTRICTED); $can_chown_giveaway = not sysconf(_PC_CHOWN_RESTRICTED); } From this I inferred that the purpose of this assignment was to do a

Re: S16: chown, chmod

On 2008 Nov 24, at 10:36, dpuu wrote: On Nov 23, 3:56 pm, [EMAIL PROTECTED] (Brandon S. Allbery KF8NH) wrote: I think you're seeing something other than what we are. Checking any external resource before operating on it introduces a race condition which can allow an attacker to swap reso

Re: S16: chown, chmod

On 2008 Nov 23, at 18:35, dpuu wrote: On Nov 23, 2:33 pm, [EMAIL PROTECTED] (Aristotle Pagaltzis) wrote: The API you propose does not seem to me to shorten code at all and is likely to lead to problematic code, so it seems like a bad idea. Interfaces should be designed to encourage people to do

Re: S16: chown, chmod

On 2008 Nov 21, at 14:13, Dave Whipp wrote: The restriction of chown to the superuser is a property of the OS, not the files. The example from the pod is: man pathconf -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED] system administrator [openafs,heimdal,too many ha

Re: S16: chown, chmod

On 2008 Nov 21, at 13:20, Larry Wall wrote: On Fri, Nov 21, 2008 at 09:57:30AM -0800, dpuu wrote: : On Nov 21, 9:16 am, [EMAIL PROTECTED] (Larry Wall) wrote: : > Please feel free to whack on the spec : The definition of C includes the statement that it's not : available on most system unless you'

Re: MAIN conflict in S06?

On 2008 Nov 14, at 12:14, Larry Wall wrote: On Thu, Nov 13, 2008 at 07:19:31PM -0600, Patrick R. Michaud wrote: : S06:2362 says: : : You can get the current routine name by calling C<&? ROUTINE.name>. : (The outermost routine at a file-scoped compilation unit is always : named C<&

Re: File test ops as string methods

On 2008 Nov 7, at 17:49, Mark J. Reed wrote: I'm sure this has been hashed out somewhere I wasn't looking, but i would really prefer for pathname ops not to be mixed in to the Str class. Maybe they could be put in a Pathname subclass of Str, with a simple literal syntax or short unary operator t

Re: XPath grammars (Was: Re: globs and trees in Perl6)

On Oct 2, 2008, at 10:36 , Timothy S. Nelson wrote: On Thu, 2 Oct 2008, Timothy S. Nelson wrote: Now that Perl6 is in the mix, though, I think that the best way to do it is to make roles that model eg. Nodes, Plexes (Documents), Elements, and the like, and then have operators on them do all

Re: globs and trees in Perl6

On 2008 Oct 1, at 22:23, Timothy S. Nelson wrote: On Wed, 1 Oct 2008, Brandon S. Allbery KF8NH wrote: On 2008 Oct 1, at 22:14, Timothy S. Nelson wrote: Hi all. I've enjoyed(?) reading over the February/March thread entitled "Musings on operator overloading". I've brou

Re: globs and trees in Perl6

On 2008 Oct 1, at 22:14, Timothy S. Nelson wrote: Hi all. I've enjoyed(?) reading over the February/March thread entitled "Musings on operator overloading". I've brought a few thoughts along; if they're old news, please tell me here to do more reading on it :). The Perl6 way to do this i

Re: Why no "is ro"? (Re: Subroutine parameter with trait and default.)

On 2008 Sep 24, at 17:45, David Green wrote: On 2008-Sep-23, at 5:27 pm, Michael G Schwern wrote: David Green wrote: Happily, brevity often aids clarity. The rest of the time, it should be up to one's editor; any editor worth its salt ought to easily auto-complete "ro" into "readonly". Ee

Re: adverbial form of Pairs notation question

On 2008 Sep 6, at 13:57, Larry Wall wrote: But basically I think NIL is a mild form of failure anyway, so it's fine with me if () is a form of failure that is smart enough to be I'm thinking () is the non-scalar (list, array, capture, maybe hash) version of undef, which acts like a value unle

Re: how much detail can I get from caller.want?

On 2008 Sep 1, at 15:20, Larry Wall wrote: On Mon, Sep 01, 2008 at 05:52:28PM +0200, TSa wrote: John M. Dlugosz wrote: Perhaps the supplier of the CPAN module for the nth function could also include, besides the actual function, an optimization pattern plug-in that locates the idiom in the pars

Re: Allowing '-' in identifiers: what's the motivation?

On 2008 Aug 12, at 20:39, Austin Hastings wrote: Actually, I proposed some years ago allowing "separable verbs" -- function/method/operator names with spaces in them, that could in fact bracket or intersperse themselves with other parameters. This would be a way of writing "if ... elsif ..

Re: List of captures, why?

On 2008 Aug 8, at 23:12, John M. Dlugosz wrote: Brandon S. Allbery KF8NH allbery-at-ece.cmu.edu |Perl 6| wrote: On 2008 Aug 8, at 23:06, John M. Dlugosz wrote: Why is 3;3;3 a list of captures rather than a list of lists? IIRC it has to do with providing enough information for slices and/ or

Re: List of captures, why?

On 2008 Aug 8, at 23:06, John M. Dlugosz wrote: Why is 3;3;3 a list of captures rather than a list of lists? IIRC it has to do with providing enough information for slices and/or * to work in multiple dimensions. -- brandon s. allbery [solaris,freebsd,perl,pugs,haskell] [EMAIL PROTECTED]

Re: Quick question: (...) vs [...]

On 2008 Aug 8, at 22:53, John M. Dlugosz wrote: What is the difference between (1,2,3) and [1,2,3] ? IIRC one is a list, the other a reference to a list --- which in perl6 will be hidden for the most part. so practically speaking the difference is minimal. -- brandon s. allbery [solari

  1   2   >