Re: Synposis 26 - Documentation [alpha draft]

ically scoped to the block in which they're specified. =config head3 :numbered =cut method foo($bar, $baz) { ... } =head3 CRC<, >RC<)> ... Is that =head3 numbered, or is it in a different lexical scope? (Actually, I don't see any reference to =cut in thi

Re: Flunking tests and failing code

he libraries where simplicity is more important than DWIMmery, lest a Perl bug manifest itself somewhere deep in the bowels of the test framework itself. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Solving '=' confusion: ':=' for aliasing

Chip Salzenberg <[EMAIL PROTECTED]> wrote: > On Tue, Nov 29, 2005 at 12:14:24PM -0800, Brent 'Dax' Royal-Gordon wrote: > > I'm not sure about the last two (in a lot of ways, they're more like > > := than = ), > > I don't see that. Well, f

Re: Solving '=' confusion: ':=' for aliasing

gt;N0 := ... # ILLEGAL >N0 = ... # assignment: modifies N0 I'm not sure about the last two (in a lot of ways, they're more like := than = ), but it's certainly far better than the status quo. I suppose that copying looks like: S0 := copy S1 -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Classification syntax [Was: Renaming grep]

e long ago on a `part` builtin? I certainly wrote List::Part based on that discussion... -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: perl6

the "Status" page on dev.perl.org/perl6 is hopelessly out of date; that should probably be rectified.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Hyphens vs. Underscores

the hyphen, simply type something like `use hyphens;` and you can use hyphenated identifiers in the surrounding scope. And unlike Ruby, this will be easy to do unambiguously: just override the Perl 6 grammar's identifier rule. All the edge cases will be resolved by the longest token principle, so `foo-bar-baz` will be an identifier. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Hashing: avoid MD5 and SHA-1; use SHA-2 or Whirlpool

ptographers need to do a lot of theoretical work on hashing--they don't really know how to design a strong algorithm yet.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: HLL Debug Segments

pragma, it should have the syntax of a pragma. Use a leading dot; you'll thank yourself later. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Ways to add behavior

onists could make jokes about "reproducing after their kind". > Some of us could make either kind of joke. But perhaps it wouldn't > be kind. Flavor. (Shades of CLOS, but we're already building the most flexible object system since it...) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: new sigil

Less than . Method call on topicMethod call > (technically unused)Greater than / Anonymous rule Divide ? Boolify There are very few unary operators available, and none (besides the user-defined backticks operator) unused in both term and operator context. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: What the heck is a submethod (good for)

hink they might actually be a sort of syntactic sugar for inserting `call` in the method body, but that's an implementation detail, really... -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Proposal to make class method non-inheritable

tance. Removing features simply because their implementation is inconvenient is not The Perl Way. If it were, Perl 6 would be Java With Sigils. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: my $key is sensitive;

ctively encrypting that area of memory--but without a minimum standard there's no point in supporting the feature at all. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: rx ops and support is deprecated

ops were an early experiment based on an incomplete understanding of the problem. I wrote the optimized int stack too for the rx ops--are you planning on keeping that? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

my $key is sensitive;

grammer's assistance (by calling a "wipe" function or making sure a destructor is correctly called), and optimizers have been known to "helpfully" remove such code. Many higher-level languages, including Perl 5, make it hard to know when a piece of data is being overwritten,

Re: [perl #16622] [PATCH PDD07] Document struct naming conventions

Yet another year has rolled by. Do you still want this change to be > considered? Certainly. Note that the naming conventions are now being followed by Interp and friends. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: item and slurpy

'll fire the first shot: type names should be nouns, not adjectives. But Pugs's internal type names are fairly irrelevant, as long as they have the right names on the outside. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

perl6-all@perl.org

{ ... print $ERR: @msg; return [EMAIL PROTECTED] #but true; } return; } I rather like that non-lexical use of junctions. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Optimizer Documentation

the loop, TURNED OFF (not currently working) =back 4 =head1 AUTHOR Curtis Rawls <[EMAIL PROTECTED]> -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

[RELEASE] WWW::Kontent 0.02: Release and revelations

Perl 5 equivalent. I could not have done this project without the support of Google and the Perl Foundation, especially my mentor at TPF, Ovid. Nor would this project be possible wtihout the efforts of the Perl 6 design team and the Pugs implementation team. Thanks to everyone involved. Share and enjoy, -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Classes as special undefs

tax: my Dog $spot .=new(); Falls out of it quite naturally. On the other hand, there are other things that don't work quite so well: my Dog $spot; $spot.can('bark');# Not until he's instantiated... On the gripping hand, maybe you should have to ask the metaclass

Re: Perl 6 Meta Object Protocols and $object.meta.isa(?)

TSa <[EMAIL PROTECTED]> wrote: > you wrote: > > Perl 6 in its unannotated form is also (mostly) a typeless languages, > > with only the five builtin types, much like Perl 5 is. > > Counting the sigil quadriga as 4, what is the fifth element? > And $it.does(LookGood

Re: undef.chars?

rs $undef" is just the > indirect object form. Didn't $Larry rule that method calls on undef return undef, for the same reason array and hash subscripting does? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

[RELEASE] WWW::Kontent 0.01

ar expressions. You will also need a SQL database engine and the Perl 5 DBI drivers to access it. I am rather excited about this project, and I hope you will be too. Share and enjoy, -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Curious use of .assuming in S06

woof ::= &bark:(Dog).assuming :pitch; > > Why is it allowed to omit comma between adverbial pairs, and even > omit parens around method call arguments? Is .assuming a special form? Isn't this just another form of the syntactic rule that gives us @array.grep:{ ... } ? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

$value.confess()

however, this would probably be a global setting, not a lexical one. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Exposing the Garbage Collector

rks by interfacing with the garbage collector, keeping an array of weak references, or waving a wooden wand and yelling "Accio objects" is completely up to the metaclass in question. (Sorry, been reading too much Potter lately...) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: s/rx.ops// ?

Will Coleda <[EMAIL PROTECTED]> wrote: > What's the plan for the regular expression ops, given PGE? As the guy who wrote them, I think at this point that they're basically unsalvageable, save the intstacks and *maybe* the bitmap handling code. -- Brent 'Dax' R

Re: Tail method calls, can(), and pre-currying

On 21/07/05, Adriano Ferreira <[EMAIL PROTECTED]> wrote: > But is there any other case where we need an explicit tail call with "goto"? When the callee uses `caller -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Do I need "has $.foo;" for accessor-only virtual attributes?

programmers will get wrong half the time, and which you don't even have enough syntax to cope with *anyway*. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Tail method calls, can(), and pre-currying

ference, in this case being invoked as a tail call. Of course, this adds *another* piece of syntax to an already large language, so I'm not sure if it's a good idea. Am I missing something? How do you think a tail method call should be performed? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Strange interaction between pairs and named binding

ork with. This would help to fix the problem without creating a new SuperPair type or something similarly silly. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: field `_crypt_struct' has incomplete type

86 laptop and my AMD64 desktop. My x86/Gentoo server is unaffected. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: proposal: binding with a function

and call it a day. IIUC, traits like `is exported` are attached to the container, not the name; since aliasing connects a name to a container, you should be fine on that front. (If it doesn't work, that's because `is exported` does something funky that `alias` would have to treat as a s

Re: proposal: binding with a function

bytes ::= &kilobyte; I'm not really sure what behavior you have in mind for alias. (By the way, a simple name like "alias" is ambiguous about argument order, where an operator isn't.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Pondering the unification of @MULTI and get_params

.param Str $P1 .param Array $P2 fold -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: %hash1 >>...<< %hash2

e this It does? I thought that when [EMAIL PROTECTED] != [EMAIL PROTECTED], the shorter one got "extended" with undefs... -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Attack of the fifty foot register allocator vs. the undead continuation monster

there are tied variables present which might do strange things like that, the compiler should emit a PIR directive saying "anything goes in this section". Perhaps some languages will always do that, but that's the price of working in those languages. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: How much do we close over?

s as optimizing Parrot's continuation-based sub calls into bsr/ret where possible. Hmm...maybe the answer is that most destruction isn't guaranteed to be timely, and any object which *is* guaranteed to have timely destruction is illegal to close over unless the programmer marks it as okay.

Re: Transparent / Opaque references

Juerd <[EMAIL PROTECTED]> wrote: > There is no way to get an anonymous rw scalar, is there? There's always the Perl 5 hack: \do { my $x } Although that's not truly anonymous, I suppose. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Argument Type Checking

se modules are special (pragmata), while intercaps modules are normal (modules and classes). Similarly, all-lowercase types are special (unboxed), while intercaps types are normal (boxed classes). -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Perl development server

Andy Bach wrote off-list: > Isn't Abigail the golfer, YA excellent PH, FunWithPerl, er guy? > > I think camels are Fido and Amelia: > http://www.perlmonks.org/?node=31716 You're right, of course. I knew it was one of those A names... -- Brent 'Dax' Royal-Gor

Re: Perl development server

On 5/23/05, Juerd <[EMAIL PROTECTED]> wrote: > Also, this new machine needs a hostname. Please help me think of a cute > name! I prefer a short hostname with less than 9 letters. I seem to remember that the camel's name is Abigail... -- Brent 'Dax' Royal-Gordon &

Re: Roles and BUILD

would need it too...) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: ^method ?

other languages use "this", "self", and even "me", and few people complain about a particular language's choice. (My suggestion would be "o" or "O", as suggested in another thread, but I'm certainly not attached to those keywords.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: Plethora of operators

w." *a few more seconds* "Holy /f---/." I think that means this should be in core. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker

Re: trait and properties thru getter/setters

On 5/13/05, Larry Wall <[EMAIL PROTECTED]> wrote: > On Fri, May 13, 2005 at 12:26:22PM -0700, Brent 'Dax' Royal-Gordon wrote: > : my $b = $a is foo($bar); > > As we currently have it, that is not legal syntax. "is" may only > be applied to declaratio

Re: trait and properties thru getter/setters

n eval? > > My question is more generic than my example. > I may not know at compile time what is the value/trait name and its > value. Well, the value's pretty easy--just pass in a variable: my $b = $a is foo($bar); As for the name, I'd be surprised if the standard

Re: Binding to a sub's return value

to a copy of $foo's value, 42. Really? Because the default parameter binding is constant reference, last I checked. I actually like that answer. It means that you can bind the return value, but you can't mutate it, unless the function 'is rw'. (And perhaps you could mark i

Re: reduce metaoperator

mon use for this--isn't common enough an operation to need such a compact syntax; I can think of more useful meta-ops, like one that tags each result with the operands that created it, allowing junctions to be used for the stuff people currently complain they can't be. multi sub *infixme

Re: Formal Parameters To While Block

;is lazy" > (another hint that it's the wrong name). To start off the name game: `is deferred`? `is closure`, `is coderef`, `is sub`? `is condition`? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junctions of classes, roles, etc.

ans "This variable can contain either a `Str` or an `Int`." (Actually, it means "this variable can contain anything consistent with a Str or Int", which also includes subclasses and certain junctions.) When you see a declaration like: my Foo $bar; Think of it as being

Re: Junctions of classes, roles, etc.

this is? sub foo(Str | Int $bar) { ... } Or this one, which is even more important? sub foo(Any | Junction $bar) { ... } -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: [RFC] assign Px, Py

y assign Px, Py copy values > > future: > >Px := Py set Px, Py >Px = Pyassign Px, Py > > This would much more resemble the HLL's (and programmers) POV. Sounds like a good idea to me. For completeness, can we come up with a clone

Re: alarm() and later()

Larry Wall <[EMAIL PROTECTED]> wrote: > Assuming we > rehuffmanize "kill" to "sendsignal" or some such, we have: "signal" is a verb as well as a noun. sub alarm ($secs) { { signal $*PID, Signal::ALARM }.cue(:delay($secs)); } It even read

Re: Context of hash slices; quotation adverbs

y, that makes me wonder: is there a difference between scalar context and one-element array context? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Truely temporary variables

to work on lexicals, of course.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Hyper operator corner case?

ty,$identity,$identity), where $identity's value is determined by a table something like this: infix:<+>0 infix:<->0 infix:<~>'' infix:<*>1 infix:1 infix:<%>mumble infix:1 I could be wrong, though; I can't find any support for it in the design docs. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Slicing conflict

Larry Wall <[EMAIL PROTECTED]> wrote: > On Tue, Apr 12, 2005 at 12:08:43AM -0700, Brent 'Dax' Royal-Gordon wrote: > : @foo[1,3; *; 7] > : > : Which I rather like. > > Me too. Unless my memory is failing me, I believe that's what S09 > already specifi

Re: Slicing conflict

umfix rule.) By the way, this also shortens the common idiom: @[EMAIL PROTECTED] To simply: @foo[3...] Which strikes me as a win. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: [perl #34912] Badly balanced at classes/pmc2c2.pl

on number like Subversion. SVN revision number is an excellent idea. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Subversion in the wings

Robert Spier <[EMAIL PROTECTED]> wrote: > Any questions? I assume current committer bits will be transitioned over too? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Configuration (was Re: Monthly Release Schedule)

on't require a 'make' (and won't have to attempt to make different 'make's work); all you'll need is a compiler, linker, and C library. This also implies that configure.pbc and build.pbc will probably have to be carefully written to work with the limited process-mani

Re: Definitive and Complete Perl 6 Operator List

quot;terms" level isn't really exhaustive. In any case, let me know if anything's missing--or for that matter if anything's there that shouldn't be. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Passing on the hat

Generation" (aka Topaz). Chip's a darned sharp guy, > desperately over-qualified, and one of the few people I know who can > do off-the-cuff MST-ing of modern cinema. Congratulations to Chip, our new Fearless Leader. And thanks for your time and guidance, Dan--Parrot wouldn&#x

Re: Slices

lying string, would we get the OP's behavior for free? say $string.chars[-1]; $string.points.splice(0, 2, "Hello"); # Or "Hello".points -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: New S29 draft up

uot;lamda x: x + $y"), :lang('python'); Since as long as we're huffmanizing, eval STRING deserves to be longer than do STRING. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: [Fwd: Re: [RFC] A more extensible/flexible POD (ROUGH-DRAFT)]

switching to square brackets is necessary. By the way, I think I've seen a few people suggest some sort of syntax-switching mechanism for "Pod6". The day people have to think about what dialect of Pod they're using is the day Pod dies as a useful documentation language. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: [Fwd: Re: [RFC] A more extensible/flexible POD (ROUGH-DRAFT)]

east, Pod has five goals: 1. Simple. 2. Adequate. 3. Easy to write. 4. Easy to convert. 5. Readable without a formatter. #5 may be last on the list, but it's not least. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: A possible solution for s?pintf

polate method calls as well. You can even do something like this if you want to perform bulk formatting: say join ' ', ($n1, $n2, $n3) >>.as('%d'); Or, if that's not quite sufficient: say map { .key.as(.value) } $num => '%d',

Re: some misc Perl 6 questions

o for the relationship to work both ways, each class would have to mark the other as trusted. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Optional binding

); y = 1 2 3; z = The $y is implicitly typed Any, and Ref of Array (or maybe just Array) is consistent with Any; hence $y receives [EMAIL PROTECTED] -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Sets vs Junctions

hich could easily be Any). -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

Perl 6 scalar datatype to a variable is an abomination). Point of consideration: is accidentally autothreading over a junction any more dangerous than accidentally looping forever over an infinite lazy list? -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hack

Re: Lingering questions about Junctions.

ne(3,4) cmp all(2,5) = undef (no conditions match) one(3,4) cmp any(1,6) = undef (no conditions match) any(1,6) cmp one(3,4) = undef (no conditions match) Happily, all of these are commutative (is this generally true?), and the Cs would be treated as 0s. So this actually would work, although it would sort in an...interesting...order. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

call to C to be junctions, the object argument is another matter entirely: #!/usr/bin/perl6 # naive tee $OUT=$OUT & open("> $_") for @ARGS; print or die "Can't write to $!.filename: $!" for *$IN;# Or however it's done this week -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

programmers probably won't use the @_ behavior, and likely won't be using slurpy parameters either, while more experienced programmers will know better. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

xt, though I could be wrong.) (The array of junctions is negotiable, by the way; whatever it is, though, it should probably be the same as the default meaning for list returns from an autothreaded function.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

x ** 2", for example.) Junctions are equivalent to the English sentence "Get eggs, bacon, and toast from the store". (In Perl, that'd be something like C<< $store->get("eggs" & "bacon" & "toast") >>.) It's just a bit of orthogonality that allows you to give "eggs, bacon, and toast" a name and use it later. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I used to have a life, but I liked mail-reading so much better."

Re: Junction Values

Likewise All so that a newbie doesn't confuzzle himself. Personally, I'd rather have a chain saw than a nail trimmer, even if I'm less likely to hurt myself with the nail trimmer. And it looks like we'll have a warning or stricture to keep newbies from chopping their legs off an

Re: Retry: ITypes and VTypes.

, what do you think this does? sub foo(@arr) {...} foo($var); I would assume the answer is "syntax error". (Remember, array parameters don't slurp in Perl 6 unless they have a *.) -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker &quo

Re: Retry: ITypes and VTypes.

signatures is correct. That, and types of hash keys. :) Either that, or the Ref value type is designed to wrap an implementation type. I'm not sure which is the case. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "For those of you that ca

Re: test_main.c oversight

William Coleda <[EMAIL PROTECTED]> wrote: > Then lets remove the file to avoid further confusion. test_main.c is being retained as an example of a non-trivial, but still clean, Parrot embedding. imcc/main.c is way too complicated and incestuous with internals to fill this role. -- B

Re: forany, forall...

on is true for any element in a list, do something. if any(@list) > 10 { ... } -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "For those of you that can't spell, this site also contains free imags, iamges, imges, picturs, pcitures, picktures, picturess, and pistures."

Re: Native data structure for parrot?

ray PMC. You can also get at a C-level struct using the ManagedStruct and UnManagedStruct PMCs, though access is a bit clumsy IIRC. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I might be an idiot, but not a stupid one." --c.l.p.misc (name omitted to protect the foolish)

Re: svn

Michael G Schwern <[EMAIL PROTECTED]> wrote: > 1) Are they easily available on all the platforms Parrot is? Various > Unixen, OS X, Windows. Is there any hope for a VMS port? Can we add "are there GUIs for Windows, OS X, and other platforms with wimpy users?" ;^) -- Br

Re: specifying the key Type for a Hash

Matt Diephouse <[EMAIL PROTECTED]> wrote: > On Tue, 7 Dec 2004 00:39:08 -0800, Brent 'Dax' Royal-Gordon > > my Patient @byid[Int $id] { > > select_patients("SELECT * FROM patients WHERE patientid = ?", > > $id)[0]; > >

Re: specifying the key Type for a Hash

select_patients( "SELECT * FROM patients WHERE lastname = ? AND firstname = ?", $last, $first ); } ... } -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I might be an idiot, but not a stupid one." --c.l.p.misc (name omitted to protect the foolish)

Re: pull & put (Was: Angle quotes and pointy brackets)

h/pull). Why not > rename pop to pull, and use something like put/take for shift/unshift? That goes way beyond offending "shell heritage". That actively opposes sixty years of computer science terminology setting "push" and "pop" in opposition. (Well, maybe not *s

Re: pull & put (Was: Angle quotes and pointy brackets)

h to negate that. But then, I'm a little biased. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I might be an idiot, but not a stupid one." --c.l.p.misc (name omitted to protect the foolish)

Re: iteration (was Re: Angle quotes and pointy brackets)

ed for.) Also note that there's no difference between iterating over a lazy copy of an array, and iterating over a lazy copy of a lazy copy of an array, except for the amount of indirection; thus, there would be no need for for() to distinguish between C and C (though both of those forms might

Re: state vs my

with an obscure name. my $x if 0; I know it's *going* away, but it hasn't *gone* away yet. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker "I might be an idiot, but not a stupid one." --c.l.p.misc (name omitted to protect the foolish)

Re: Angle quotes and pointy brackets

John Siracusa <[EMAIL PROTECTED]> wrote: > On 11/30/04 9:54 PM, Matt Diephouse wrote: > > use CGI «:standard»; > > [...] > > use CGi <:standard>; > > Who is doing this? I'm just saying... > >use CGI ':standard'; And won

Re: Angle quotes and pointy brackets

} use File::Copy qw(mv cp); ... # I do hope we get something better than #line. eval "#line 1 '-me'\n" ~ @ARGS.shift; } } perl -me 'say "This is my one-liner!"' One-liners with no specific support in the core--and it's differ

Re: Angle quotes and pointy brackets

ight be able to take a page out of C#'s book with @"" as the short form of the raw quoting construct. (Or something like that--I suspect C# picked @ because it's otherwise unused.) Actually, if we do something else with backticks, we can steal backticks for totally raw quoting...

Re: [perl #32643] [TODO] Remove Perl* PMCs from opcodes

Will Coleda wrote: > The following opcodes return 'PerlUndef' on failure, instead of 'Undef' or > null. > > open, socket, fdopen, dlfunc, dlvar, find_global Patch attached that changes all these to Undef. -- Brent 'Dax' Royal-Gordon <[EMAIL PR

Re: IEEE 754 double floats

as its floating-point type. The problem is probably with the precision of 'print N0'; try using the 'sprintf' opcode and printing the resulting string instead. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker There is no cabal.

Re: [PATCH] A little more Configure info

ly gcc....yes. Thanks, applied. -- Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> Perl and Parrot hacker There is no cabal.

Re: [perl #32356] AutoReply: [PATCH] update to embed.pod

ernals-only header--including it exposes all of Parrot's guts to the embedder. Note this comment at the top of parrot.h: # /* Only parrot core files should include this file. #Extensions should include . #Programs embedding parrot should include . # */ And the define a few lines down:

  1   2   3   4   5   6   7   8   9   >