HaloO,
Larry Wall wrote:
On Tue, Apr 11, 2006 at 12:41:30PM +0200, TSa wrote:
: I'm unsure what the outcome of the recent long dot discussions is
: as far as the range operator is concerned.
.. is always the range operator. The dot wedge just has a discontinuity
in it there. I can't think of
Nicholas Clark wrote:
./src/library.c:*prefix_str = CONST_STRING(interpreter, pwd);
I've fixed that one now and the code in c2str.pl verifies that it gets
exactly two quote chars.
Nicholas Clark
leo
Patrick R. Michaud wrote:
I'm now thinking that the problem has to be either in load_bytecode
or in the .pbc file itself (PGE.pbc).
[ ... ]
Lastly, to really indicate that the problem seems to be in
.pbc handling somewhere -- try changing line 91 of
# New Ticket Created by Will Coleda
# Please include the string: [perl #38903]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=38903
Tcl uses globals in the '_Tcl' namespace to hold information about
the
The current top level namespaces are 'Tcl' and '_Tcl'. According to PDD21, this
should be tcl
and _tcl.
Author: particle
Date: Wed Apr 12 09:41:22 2006
New Revision: 12189
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
[PDD21]
~ namespaces passed to {find,store}_global ops are relative to HLL namespace
Modified: trunk/docs/pdds/pdd21_namespaces.pod
Hi,
Calling Parrot_init explicitly on a Parrot_Interp returned by Parrot_new is
useless.
(Parrot_new does it itself and Parrot_init doesn't do anything on already
initiated interpreters)
Because it makes the api more complicated i propose to remove it from
the docs.
I attach a patch which
Author: particle
Date: Wed Apr 12 10:48:10 2006
New Revision: 12190
Modified:
trunk/docs/pdds/pdd21_namespaces.pod
Log:
[PDD21] modify doc to match current code behavior
~ define HLL Root Namespace
~ modify HLL User-Created Namespace definition
~ namespaces passed to {find,store}_global ops
On Apr 12, 2006, at 18:00, Will Coleda (via RT) wrote:
Tcl uses globals in the '_Tcl' namespace to hold information about
the interpreter. But now:
find_global '_Tcl', 'foo
doesn't work, because it's relative to the current namespace, which
is usually Tcl.
s/usually Tcl/usually tcl/ #
# New Ticket Created by Will Coleda
# Please include the string: [perl #38907]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=38907
The following code makes parrot bus error:
.sub foo
.include 'interpinfo.pasm'
On Wednesday 12 April 2006 00:06, TSa wrote:
Doesn't that discontinuity devalue the long dot? Its purpose is
alignment in the first palce. For a one char diff in length one
now needs
foo. .bar;
self. .bar;
instead of
foo .bar;
self.bar;
Or even:
foo.bar;
I *still* don't understand the problem this long dot is trying to
solve.
I'm a bit with you, there. I can see why you might want to do
$query
.fetchrow($i)
.selectcolumn($j)
.say;
rather than
$query.
fetchrow($i).
selectcolumn($j).
say;
but surely
$query.
.fetchrow($i).
.selectcolumn($j).
TSA wrote:
I *still* don't understand the problem this long dot is trying
to solve.
It's trying to solve the fundamental ambiguity of:
foo .bar
Which might be:
foo().bar
or might be:
foo(.bar)
The way we solved it is by saying that, anywhere a term is expected, a
sequence
On Apr 11, 2006, at 19:03, Chip Salzenberg wrote:
1. Value Model for value objects
which is why saying 'stick with [ISNP]'
is synonymous with 'no value types' [of that nature].
Ack. That's certainly an optimization thingy (e.g. native 'complex'
type ...) and not targeted
14 matches
Mail list logo
