Bernhard Schmalhofer wrote:
One thing that I noticed is the naming of the new field UUID.
||| The UUID is |
||| computed by applying the hash function specified
in|
||| the UUID type field over the entire packfile
not |
||
Leopold Toetsch wrote:
Indeed. But we probably want to have an UUID to identify
loaded .pasm/.pir/.pbc to avoid loading duplicates.
The UUID as proposed was intended for that; I just hashed up the
definition in the PDD. Er, no pun intended.
As a side note: distinct PBC segments for
HaloO,
Stevan Little wrote:
As for how the example in the OP might work, I would suspect that
super would not be what we are looking for here, but instead a
variant of next METHOD.
I'm not familiar with the next METHOD syntax. How does one get the
return value from it and how are parameters
HaloO,
Stevan Little wrote:
On 10/2/06, Jonathan Lang [EMAIL PROTECTED] wrote:
This notion of exclusionary roles is an interesting one, though. I'd
like to hear about what kinds of situations would find this notion
useful; but for the moment, I'll take your word that such situations
exist and
Mark J. Reed:
Aaron Sherman:
Proposal: A sigil followed by [...] is always a composer for that
type.
%[...] - Hash. Unicode: ?...?
@[...] - Array. Unicode: [...]
? - Seq. Unicode: ?...?
[...] - Code. Unicode: ?...?
|[...] - Capture.
TSa wrote:
I'm not familiar with the next METHOD syntax.
It's simple: if a multi method says next METHOD; then execution of
the current method gets aborted, and the next MMD candidate is tried;
it uses the same parameters that the current method used, and it
returns its value to the current
A thread on p5p recently brought up the idea of multi-language exceptions.
That is, instead of throwing exceptions with English C-strings embedded in
the source code, use a localization system.
If there'll soon be a push to clean up all of the uses of exceptions in the
source code (to make
Yes please!
On Oct 6, 2006, at 4:27 PM, chromatic wrote:
A thread on p5p recently brought up the idea of multi-language
exceptions.
That is, instead of throwing exceptions with English C-strings
embedded in
the source code, use a localization system.
If there'll soon be a push to clean up
To my surprise, I found a 'ctx' member in struct Parrot_sub. It
appears that this is only used for the autoclose feature, which AFAICS
is not documented. The only place it is mentioned is in four
t/op/lexicals.t cases (though it is also used in three t/pmc/exception.t
cases; see the patch).
On Tuesday 03 October 2006 13:41, Aaron Sherman wrote:
This contains the Makefile, README, .pg grammar, a -harness.pir that
executes the parser on a sample string and dumps the parse tree and a
-stress.pir that runs 50,000 trial runs to see how fast PGE is (not too
shabby is the answer, as it
10 matches
Mail list logo
