A first patch is in CVS. Imcc now understands the syntax:
set_p_pc P0, 0 # load PMC constant no. 0
The explicit arguments are necessary to disambiguate
set P0, 0 # assign integer 0 to P0
This isn't much useful per se, as a compiler/you doesn't know the
constant index of a PMC co
Brent 'Dax' Royal-Gordon <[EMAIL PROTECTED]> wrote:
> ... We could probably do something very clever to abstract it,
> like load all the constants into a reserved, dynamically-sized set of
> registers starting at [INSP]32.
That doesn't work. Registers are accessed per interpreter/thread and now
David H. Adler wrote:
Mine is in
/usr/local/lib/perl5/site_perl/5.8.5/darwin-2level/Devel/Cover.pm
On OS X (and other systems, I'm sure) stuff sometimes gets installed
under architecture specific directories like that.
As mentioned elsehwere, perldoc -l is your friend.
dha
Yes, as I subsequ
Randy W. Sims wrote:
Is it correctly installed: `perl -MDevel::Cover -e1`
If so, you can find it with: `perldoc -l Devel::Cover`
BTW, A quick way to view the source is: `perldoc -m Devel::Cover`
Cool! Somehow the -l and -m options to 'perldoc' were completely
unknown by me.
I can see I'll be u
Nicholas Clark <[EMAIL PROTECTED]> wrote:
> On Fri, Oct 29, 2004 at 05:47:55PM +0200, Leopold Toetsch wrote:
>> classes/*.c is created by the bytecode compiler classes/pmc2c2.pl. Most
>> of the actual code is in lib/Parrot/Pmc2c.pm.
>>
>> The created C code could need some improvements:
> Can I ad
Ok, next is committed. The existing constant syntax is extended:
.const var_or_ident = "initstring"
Currently only subroutine constants are supported, e.g.
.const .Sub $P0 = "foo"
.const .Sub func = "foo"
The actual opcode emitted is "sub_p_pc" with the index of the subroutine
constant a
On Oct 30, 2004, at 12:58 AM, Leopold Toetsch wrote:
Nicholas Clark <[EMAIL PROTECTED]> wrote:
On Fri, Oct 29, 2004 at 05:47:55PM +0200, Leopold Toetsch wrote:
* The created C code could benefit from #line directives to track
where
C code came from the input .pmc file, so that compiler errors a
On Fri, Oct 29, 2004 at 09:10:30PM -0400, James E Keenan wrote:
> Yes, as I subsequently discovered, it's in the mysteriously named
> 'darwin-2level' directory.
This is the "architecture specific" directory where any modules with a
non-portable component (read: compiled C code) goes.
--
Michae
* James E Keenan ([EMAIL PROTECTED]) wrote:
> and in the corresponding /blib/lib directory. Of course, I expected it
> to be here as a residue from its installation ... but I expected it to
> be in some 'lib' directory as well.
>
> Can anyone clue me in?
I have a handy script I keep in my ~/bi
On Fri, Oct 29, 2004 at 05:19:35PM +0200, Leopold Toetsch wrote:
> The method_lookup doesn't have a vtable indirection. And having a direct
> array lookup doesn't really scale. So the actual code is a bit more
> complicated (and in no way optimized).
Something that just struck me reading this who
I'm now the point man for contacts on getting into the Phalanx
repositories. Also, I'm going to be reorganizing the existing
repositories a bit, just to help standardize. SouthFlorida, have you
done anything on Error or URI yet? If not, I'm going to restart them.
Any other hoplites care to c
11 matches
Mail list logo
