JMD Consider the words that may be used to introduce a block for a special
JMD purpose, like
JMD
JMD BEGIN
JMD END
JMD INIT
JMD CATCH
JMD etc.
JMD
JMD What do you call those?
Well, lessee. The Common Lisp spec calls them situations in the
definition of (eval-when)...
JMD They are not even
On Thu, Apr 10, 2008 at 2:16 AM, Mark J. Reed [EMAIL PROTECTED] wrote:
JMD Consider the words that may be used to introduce a block for a special
JMD purpose, like
JMD
JMD BEGIN
JMD END
JMD INIT
JMD CATCH
JMD etc.
JMD
JMD What do you call those?
Well, lessee. The
On Thu, Apr 10, 2008 at 2:26 AM, Chas. Owens [EMAIL PROTECTED] wrote:
It looks like they already have a name in S04: Closure traits*.
* http://dev.perl.org/perl6/doc/design/syn/S04.html#Closure_traits
I don't know, it seems like any value might happen to both be a
closure and have traits,
On Thu, Apr 10, 2008 at 2:29 AM, Mark J. Reed [EMAIL PROTECTED] wrote:
On Thu, Apr 10, 2008 at 2:26 AM, Chas. Owens [EMAIL PROTECTED] wrote:
It looks like they already have a name in S04: Closure traits*.
* http://dev.perl.org/perl6/doc/design/syn/S04.html#Closure_traits
I don't
# New Ticket Created by Andreas Rottmann
# Please include the string: [perl #52666]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52666
Well, the subject sais it all. For implementing EQ? efficiently (using
the
On Wed Apr 09 20:52:37 2008, infinoid wrote:
I've implemented a workaround (manually specifying build rules for the
subdir files) in r26899, to keep us rolling in the meantime. Please
revert that when a real fix comes around.
And after a little more research, I've found the proper fix. GNU
# New Ticket Created by James Keenan
# Please include the string: [perl #52706]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52706
While conducting 'make test' on Darwin last night, I noticed that the process
was
On Wed, Apr 9, 2008 at 10:31 PM, John M. Dlugosz
[EMAIL PROTECTED] wrote:
Consider the words that may be used to introduce a block for a special
purpose, like
BEGIN
END
INIT
CATCH
etc.
What do you call those? They are not even special named blocks because
that is not the block
HaloO,
John M. Dlugosz wrote:
Can you give a pointer to where this was discussed?
It was said by $Larry in the Adding linear interpolation
to an array thread where I also tried to explain co- and
contravariant typing of container types.
Regards, TSa.
--
The Angel of Geometry and the Devil
On Thu, Apr 10, 2008 at 08:52:38AM -0700, jerry gay wrote:
: On Wed, Apr 9, 2008 at 10:31 PM, John M. Dlugosz
: [EMAIL PROTECTED] wrote:
: Consider the words that may be used to introduce a block for a special
: purpose, like
:
: BEGIN
: END
: INIT
: CATCH
: etc.
:
: What do you
Mark J. Reed markjreed-at-mail.com |Perl 6| wrote:
Now you've lost me. I was pretty sure that was the block name. AIUI,
you can give arbitrary names to any block, and these names function
the same way (i.e. can be used in flow control statements), but they
also happen to control when the block
As I read it, the original question was about the actual keyword -
e.g. the word BEGIN - as distinct from the block it's attached to.
Though I agree we need a general term for the latter, the name event
block seems to imply that BEGIN et al are events, which might be ok
or might cause confusion
On Thu, Apr 10, 2008 at 01:35:57PM -0400, Mark J. Reed wrote:
: As I read it, the original question was about the actual keyword -
: e.g. the word BEGIN - as distinct from the block it's attached to.
: Though I agree we need a general term for the latter, the name event
: block seems to imply that
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #52712]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52712
Today I tried to test if an imcc patch worked and ran into the following
weird
Hey,
I *thought* I'd try and clean up an easy one, so I took
src/key.c
src/key.c: In function `key_integer':
src/key.c:368: warning: switch missing default case
After a little poking I tracked the rest of the Key__FLAG s down to
include/parrot/key.h (and pobj.h) [1] and so I rearrainged the
Just so you don't think this is warnocked, I'm looking at it, and
thinking about it. By and large it seems to be going the right
direction, though I've naturally got a number of quibbles.
Probably each quibble needs to be a separate thread though, since
many of them will probably breed
On Thu, Apr 10, 2008 at 11:23 AM, Larry Wall [EMAIL PROTECTED] wrote:
On a larger question, I'm wondering if it's time to slush/freeze
the Synopses as historical documents and put all spec effort into
the new form (presumably as a wiki that knows how to serialize into
a document). I don't
On Thu, Apr 10, 2008 at 12:11:05PM -0700, jerry gay wrote:
: On Thu, Apr 10, 2008 at 11:23 AM, Larry Wall [EMAIL PROTECTED] wrote:
: On a larger question, I'm wondering if it's time to slush/freeze
: the Synopses as historical documents and put all spec effort into
: the new form (presumably
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #52710]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52710
Hey,
I *thought* I'd try and clean up an easy one, so I took
src/key.c
On Thu, 10 Apr 2008 10:53:31 -0700
[EMAIL PROTECTED] (via RT)
[EMAIL PROTECTED] wrote:
# New Ticket Created by [EMAIL PROTECTED]
# Please include the string: [perl #52710]
# in the subject line of all future correspondence about this issue.
# URL:
Larry Wall larry-at-wall.org |Perl 6| wrote:
Just so you don't think this is warnocked, I'm looking at it, and
thinking about it.
Thanks. I thought perhaps everyone filtered it out since it had a bad
subject line.
By and large it seems to be going the right
direction, though I've
On Thu, 10 Apr 2008 13:21:23 -0700
Mark Glines [EMAIL PROTECTED] wrote:
}
+
}
Okay, without *most* of the white space changes. Oh well, I tried.
Mark
On Apr 10, 2008, at 13:29 , John M. Dlugosz wrote:
I might have misremembered, but i thought labels were followed by a
colon in Perl 6. A quick scan of the docs...
It is illegal for a provisional subroutine call to be followed by a
colon postfix, since such a colon is allowed only on an
On Thu, Apr 10, 2008 at 04:38:27PM -0400, Brandon S. Allbery KF8NH wrote:
On Apr 10, 2008, at 13:29 , John M. Dlugosz wrote:
I might have misremembered, but i thought labels were followed by a
colon in Perl 6. A quick scan of the docs...
It is illegal for a provisional subroutine call to
I've consolidated all the discussion into one reply:
The perldocs call them Five specially named code blocks, The Camel
names them individually (e.g. BEGIN block). How about phase blocks? They
control in what phase of compilation/runtime the code runs in.
I don't know, phase sounds too
# New Ticket Created by Patrick R. Michaud
# Please include the string: [perl #52718]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52718
When using Perl6Grammar to build parsers (e.g., as part of PCT),
the is
On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote:
I've consolidated all the discussion into one reply:
The perldocs call them Five specially named code blocks, The Camel
names them individually (e.g. BEGIN block). How about phase blocks? They
control in what phase of
On Thu, Apr 10, 2008 at 5:00 PM, Larry Wall [EMAIL PROTECTED] wrote:
Well, lessee. The Common Lisp spec calls them situations in the
definition of (eval-when)...
That's not bad.
Oh, sure, ignore it when I first said it, but let John quote me and
allasudden it's notable.. :-)
An
Am in transit so cannot provide a complete analysis now. However,
please look at line 40 of lib/Parrot/Manifest.pm. This line seems to
exclude all file names containing the string 'ports'. While this
correctly excludes ports of Parrot, it probably incorrectly excludes all
source files with that
From: Larry Wall [EMAIL PROTECTED]
Date: Thu, 10 Apr 2008 14:00:53 -0700
On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote:
Well, lessee. The Common Lisp spec calls them situations in the
definition of (eval-when)...
That's not bad.
FWIW, eval-when only
# New Ticket Created by Bernhard Schmalhofer
# Please include the string: [perl #52720]
# in the subject line of all future correspondence about this issue.
# URL: http://rt.perl.org/rt3/Ticket/Display.html?id=52720
When removing Parrot/HLLCompiler for RT#48030 I noticed that the docs
of
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Mark J. Reed
Sent: Thursday, April 10, 2008 4:26 PM
To: perl6-all@perl.org; [EMAIL PROTECTED]
Subject: Re: Nomenclature Question - BEGIN etc.
but tag
for the keyword feels right to me. We could just
Hi,
We have a couple of bits of OO stuff missing in Parrot.
The callmethodsupercc op isn't implemented. I'm thinking for this we
need a variant of find_method, which does the required skipping over the
current class?
We'll also need to work out how to do callmethodnextcc too, which is
On Thu, Apr 10, 2008 at 6:59 PM, Jonathan Worthington
[EMAIL PROTECTED] wrote:
Hi,
We have a couple of bits of OO stuff missing in Parrot.
The callmethodsupercc op isn't implemented. I'm thinking for this we need a
variant of find_method, which does the required skipping over the current
Yeah, it wasn't really a patch as it doesn't work. It was more of a
question 'does anybody know if it's a missing Key__FLAG or something
else' that's bringing in the unexpected (I guess) switch case value.
The code was for illustrative purposes, just tracking what I've found so
far.
On Thu Apr 10 14:16:58 2008, infinoid wrote:
Oddly, adding config/auto/macports.pm to MANIFEST didn't help. It is
copied, but I don't think this module is getting use'd, for whatever
reason.
What the heck? When I added t/steps/auto_macports-*.t to MANIFEST (in
r26916), it started working.
On Apr 10, 2008, at 18:58 , Bob Rogers wrote:
From: Larry Wall [EMAIL PROTECTED]
Date: Thu, 10 Apr 2008 14:00:53 -0700
On Thu, Apr 10, 2008 at 03:41:19PM -0500, John M. Dlugosz wrote:
Well, lessee. The Common Lisp spec calls them situations in the
definition of (eval-when)...
See my latest, in section 4.2, for a first cut on episodes. I took a first
stab at formalizing all phases of translation and execution, and documented
what was known about the episodes I knew about, especially those corresponding
to keywords that introduce an episodic block (as a
It will always be too early, and too late. There will always be
reasons not to do it till next year, and reasons you're hosed because
it wasn't done years ago. Now is all we've got at the moment...
Larry
That's how C++ was. The call to ANSI was hot on the heels of a
statement saying
On Thu, 10 Apr 2008, Mark Glines via RT wrote:
On Thu Apr 10 14:16:58 2008, infinoid wrote:
Oddly, adding config/auto/macports.pm to MANIFEST didn't help. It is
copied, but I don't think this module is getting use'd, for whatever
reason.
What the heck? When I added
Brandon S. Allbery KF8NH skribis 2008-04-10 19:41 (-0400):
On the other hand, that may be the answer right there: when-blocks.
No, this is a when block:
when /foo/ { ... }
:)
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker [EMAIL PROTECTED]
On Thu, Apr 10, 2008 at 7:41 PM, Brandon S. Allbery KF8NH
[EMAIL PROTECTED] wrote:
On the other hand, that may be the answer right there: when-blocks.
We have those already: given...when.
--
Mark J. Reed [EMAIL PROTECTED]
My suggestion:
consequential blocks
--
Met vriendelijke groet, Kind regards, Korajn salutojn,
Juerd Waalboer: Perl hacker [EMAIL PROTECTED] http://juerd.nl/sig
Convolution: ICT solutions and consultancy [EMAIL PROTECTED]
On Thu, Apr 10, 2008 at 8:49 PM, Juerd Waalboer [EMAIL PROTECTED] wrote:
My suggestion:
consequential blocks
...which would make other blocks inconsequential?
Nuh-uh.
--
Mark J. Reed [EMAIL PROTECTED]
And I'm getting somewhat similar failure on Darwin RT 52726
On Thu, Apr 10, 2008 at 05:53:10PM -0700, [EMAIL PROTECTED] wrote:
Author: chromatic
Date: Thu Apr 10 17:53:10 2008
New Revision: 26920
[OO] Optimized isa() vtable entry for Class. Instead of delegating
most of its work to isa_pmc(), this entry now performs its work
directly. This is
On Thursday 10 April 2008 18:35:00 Patrick R. Michaud wrote:
[OO] Optimized isa() vtable entry for Class. Instead of delegating
most of its work to isa_pmc(), this entry now performs its work
directly. This is slightly faster and avoids creating a temporary PMC.
The Perl 6 build
On Thu Apr 10 18:17:17 2008, [EMAIL PROTECTED] wrote:
And I'm getting somewhat similar failure on Darwin RT 52726
r26910 introduced a bug into PGE's build process -- PGE suddenly
depended on PCT, but PCT was being built after PGE. This is fixed in
r26918, and reportedly solves the remaining
I hypothesized that this problem -- which is continuing as of r26920
(Apr 10) -- originated in a recent change to a GDBM-related file within
the Parrot distribution.
[parrot] 530 $ find . ! -path '*/.svn*' -iname '*gdbm*' | xargs svn
status -v
2692026101 particle
Author: pmichaud
Date: Thu Apr 10 19:28:40 2008
New Revision: 26921
Modified:
trunk/docs/pdds/pdd26_ast.pod
Changes in other areas also in this revision:
Modified:
trunk/compilers/pct/src/PAST/Node.pir
Log:
[pct]:
* Add symbol_defaults method to PAST::Block, to simply setting
default
S06 shows how to define named-only parameters, marked with a prefix :. But
no example shows anything more than a bare parameter name. No type is ever
given!
Looking through my copy of STD.pm, I'm baffled, as it seems not to take types
in parameter lists at all.
So, is it
method bytes (
I have confirmed that this problem developed in r26790 or later.
t/dynpmc/gdbmhash.t was running properly as of 26789:
/usr/bin/g++ -o pbc_merge \
src/pbc_merge.o \
src/parrot_config.o \
src/string_primitives.o \
-L/Users/jimk/work/parrot/26789/blib/lib
It is not specified in the Synopses as I recall, but I believe that this is
useful enough that it must be made to work:
method bytes (Encoding :$encoding = .encoding)
returns Int
or even
method bytes (Encoding :$encoding = self!encoding)
returns Int
That is, a named-only
On Fri, Apr 11, 2008 at 03:26:02AM -, John M. Dlugosz wrote:
: S06 shows how to define named-only parameters, marked with a prefix :. But
no example shows anything more than a bare parameter name. No type is ever
given!
:
: Looking through my copy of STD.pm, I'm baffled, as it seems not
On Fri, Apr 11, 2008 at 03:35:37AM -, John M. Dlugosz wrote:
: It is not specified in the Synopses as I recall, but I believe that this is
useful enough that it must be made to work:
:
:method bytes (Encoding :$encoding = .encoding)
:returns Int
:
: or even
:
:method bytes
With some recent PCT-related changes I think we may want to
update the tutorials a bit.
1. Remove the custom List class.
ResizablePMCArray now has built-in shift/unshift/push/pop
methods, so we can use it directly from NQP and don't need
to create a custom List class to be able to invoke these
On Thu, Apr 10, 2008 at 09:18:38PM -0700, Larry Wall wrote:
On Fri, Apr 11, 2008 at 03:26:02AM -, John M. Dlugosz wrote:
: S06 shows how to define named-only parameters, marked with a prefix :.
But no example shows anything more than a bare parameter name. No type is
ever given!
:
:
On Thu, Apr 10, 2008 at 02:02:37PM -0700, Bernhard Schmalhofer wrote:
When removing Parrot/HLLCompiler for RT#48030 I noticed that the docs
of 'comreg'
did not match very well with reality.
pmichaud elaborated on IRC:
[...]
See also the thread on this topic at [1]. Essentially a
On Thu, Apr 10, 2008 at 11:53:00PM -0500, Patrick R. Michaud wrote:
A patch is attached making this change.
Attaching patch.
Pm
Index: src/ops/core.ops
===
--- src/ops/core.ops(revision 26926)
+++ src/ops/core.ops(working
59 matches
Mail list logo
