Uri writes:
> DC> One might also envisage a C pragma to require
> DC> that all lexicals be typed.
>
> do you mean lexical params in a sub signature? or all lexicals in the
> current scope which contains the pragma?
any(@above).
Some people will want one; some, the other. We
John Siracusa <[EMAIL PROTECTED]> writes:
> If you ask any Java programmer which is "correct", myJavaMethod() or
> My_Java_Method(), I think you'll get a straight answer.
>From experience I can assure you this is not the case. There are a
couple of (independent and mutual inconsistent) style gui
"Brent Dax" <[EMAIL PROTECTED]> writes:
> # From: Uri Guttman [mailto:[EMAIL PROTECTED]]
> # BD> equivalent) in method lookups? In other words, if
> # $spot is declared to
> # BD> hold a Dog, can we assume that it does, thus skipping
> # the check with
> # BD> 'ref' normally used for method
# -Original Message-
# From: Uri Guttman [mailto:[EMAIL PROTECTED]]
# Sent: Friday, August 24, 2001 4:09 PM
# To: [EMAIL PROTECTED]
# Cc: [EMAIL PROTECTED]
# Subject: Re: Will subroutine signatures apply to methods in Perl6
#
#
# > "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
#
#
# -Original Message-
# From: Uri Guttman [mailto:[EMAIL PROTECTED]]
# Sent: Friday, August 24, 2001 8:56 PM
# To: [EMAIL PROTECTED]
# Cc: [EMAIL PROTECTED]
# Subject: Re: Will subroutine signatures apply to methods in Perl6
#
#
# > "BD" == Brent Dax <[EMAIL PROTECTED]> writes:
...
#
I was thinking about Perl 6 today, and thought of something: if the
sigil is now part of a variable's name, does that mean that $Foo::bar
should actually be Foo::$bar in Perl 6?
--Brent Dax
[EMAIL PROTECTED]
Uri Guttman <[EMAIL PROTECTED]> writes:
> > "DC" == Damian Conway <[EMAIL PROTECTED]> writes:
>
> DC> One might also envisage a C pragma to require
> DC> that all lexicals be typed.
>
> do you mean lexical params in a sub signature? or all lexicals in the
> current scope which contains
On 8/25/01 5:12 AM, Johan Vromans wrote:
> John Siracusa <[EMAIL PROTECTED]> writes:
>> If you ask any Java programmer which is "correct", myJavaMethod() or
>> My_Java_Method(), I think you'll get a straight answer.
>
> From experience I can assure you this is not the case. There are a
> couple o
I've got the rudiments of the parrot interpreter and assembler built and
running. (I get around 23M ops/sec on a 700MHz Alpha EV6) I'm beating it up
enough to get it into a reasonably released state, so while I'm doing that...
I'm currently thinking of using .pasm as the extension for parrot as
At 11:37 PM 8/22/2001 +0100, Tim Bunce wrote:
>Larry's already said (from memory) that the distinction between ops and
>subs should be minimized or eliminated.
>
>That, together with the desire to keep parrot fairly language netural,
>leads naturally to having 'heavy' ops actually be be subs.
Yup
In perl.perl6.stdlib, you wrote:
>
>Er, okay, well scratch that example then :) But my point still stands: I
>think Perl 6 should have some sort of guidelines in this area, even if
>they're only a codification of what "the majority" of Perl authors do.
Yes. See also "perldoc perlstyle" and the
On Sat, Aug 25, 2001 at 09:40:05AM -0400, John Siracusa wrote:
> On 8/25/01 5:12 AM, Johan Vromans wrote:
> > John Siracusa <[EMAIL PROTECTED]> writes:
> >> If you ask any Java programmer which is "correct", myJavaMethod() or
> >> My_Java_Method(), I think you'll get a straight answer.
> >
> > Fr
On 8/25/01 1:51 PM, Kirrily Robert wrote:
> In perl.perl6.stdlib, you wrote:
>> Er, okay, well scratch that example then :) But my point still stands: I
>> think Perl 6 should have some sort of guidelines in this area, even if
>> they're only a codification of what "the majority" of Perl authors
> "Dan" == Dan Sugalski <[EMAIL PROTECTED]> writes:
Dan> I've got the rudiments of the parrot interpreter and assembler built
Dan> and running. (I get around 23M ops/sec on a 700MHz Alpha EV6) I'm
Dan> beating it up enough to get it into a reasonably released state, so
Dan> while I'm doing th
On 8/25/01 10:37 AM, Dan Sugalski wrote:
> I'm currently thinking of using .pasm as the extension for parrot assembly
> code, and .pbc for precompiled bytecode. [...] Can anyone think of anything
> better? They seem rather lame.
I think they're just fine, actually. I like them better than anythi
On Sat, Aug 25, 2001 at 10:37:35AM -0400, Dan Sugalski wrote:
> I'm currently thinking of using .pasm as the extension for parrot assembly
> code, and .pbc for precompiled bytecode. (Yes, the interpreter loads and
> runs compiled bytecode from disk. Wheee!) Can anyone think of anything
> better
At 06:58 PM 8/25/2001 +0100, Simon Cozens wrote:
>On Sat, Aug 25, 2001 at 10:37:35AM -0400, Dan Sugalski wrote:
> > I'm currently thinking of using .pasm as the extension for parrot assembly
> > code, and .pbc for precompiled bytecode. (Yes, the interpreter loads and
> > runs compiled bytecode fro
At 08:11 PM 8/23/2001 -0400, Robert Spier wrote:
>Just some brief comments... $0.02 or some such. :)
> > The top-level structure of the Perl source tarball should be as
> > follows:
> >
> > /README, etca few top-level documents
> > /doc/ Assorted miscellaneous documentation
At 03:22 PM 8/18/2001 -0400, Uri Guttman wrote:
>i didn't see any references to support debugging an external perl
>process. this should be designed in from the beginning, so the debugger
>API can be designed to work locally and over a pipe. the pipe can
>support an rpc or message interface which
On Fri, Aug 24, 2001 at 09:20:26PM -0700, Brent Dax wrote:
> I was thinking about Perl 6 today, and thought of something: if the
> sigil is now part of a variable's name, does that mean that $Foo::bar
> should actually be Foo::$bar in Perl 6?
Techincally 'bar' is shorthand for the complete name,
At 09:18 PM 8/24/2001 -0700, Brent Dax wrote:
>I meant that, if we
>know $spot is supposed to have a Dog in it, can we avoid checking if it
>really does (at least some of the time) and maybe shuck some overhead by
>doing so? Perhaps we only check after each assignment to $spot, and
>when we check
In perl.perl6.stdlib, you wrote:
>
>Something like perlstyle and perlmodstyle for perl 5 then?
My main purpose with perlmodstyle was to give us a starting point for a
Perl 6 style guide, in time for the Great Rewrite that's likely to
happen with most of CPAN.
K.
--
Kirrily 'Skud' Robert - [EM
I'd like to keep the code on Sourceforge from the get-go. I don't
have much experience with Sourceforge, though, and would like to talk
to someone who has. Which bits work well? Which bits aren't worth
the effort? Any tips or tricks to pass on?
Thanks,
Nat
On Sat, 25 Aug 2001, Nathan Torkington wrote:
> I'd like to keep the code on Sourceforge from the get-go. I don't
> have much experience with Sourceforge, though, and would like to talk
> to someone who has. Which bits work well? Which bits aren't worth
> the effort? Any tips or tricks to pas
24 matches
Mail list logo
