At 06:06 PM 12/11/2003 -0500, Dan Sugalski wrote:
Folks,
As IMCC's in some flux and likely to get gutted and reworked, the question
of macros has come up. (They cause some grammar issues) So, to make life
easier:
Parrot's built-in PIR and PASM parsing modules do *not* need to do macros.
(Thoug
At 12:34 PM -0500 12/11/03, Melvin Smith wrote:
At 11:57 AM 12/11/2003 -0500, Dan Sugalski wrote:
That does, though, argue that we need to revisit the global access
opcodes. If we're going hierarchic, and we want to separate out the
name from the namespace, that would seem to argue that we'd want
Folks,
As IMCC's in some flux and likely to get gutted and reworked, the
question of macros has come up. (They cause some grammar issues) So,
to make life easier:
Parrot's built-in PIR and PASM parsing modules do *not* need to do
macros. (Though they do need to do .const things) Macro assembl
Gordon Henriksen <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch <[EMAIL PROTECTED]> wrote:
>> What about:
>>
>> getinterp P2
>> set P1, P2['global';'namespace';'hierarchy';'thingname']
> What if global.namespace happens to be autoloaded or otherwise magic?
> Will the get_keyed break down and do
On Thu, 2003-12-11 at 12:05, Gordon Henriksen wrote:
> It is truly remarkable the lengths that Perl programmers seem to be
> willing go to in order to hide a function call or obscure the existence
> of an object. :)
Not all of the poly- and allomorphism in the world comes from
"traditional" objec
Dan Sugalski wrote:
Yep, though that's a big part of it. postgres.pasm is generated from
postgres.declarations, FWIW--there's a script in the library somewhere.
Is /parrot/build_tools/build_nativecall.pl the script in question and if
so whats its usage.
I have done postgres.declarations, please se
Melvin Smith <[EMAIL PROTECTED]> wrote:
> my $foo = Oracle::Instance::DEV1::db_block_buffers;
>
> The namespace lookup in Oracle::Init checks the Oracle config
> parameters which is external code.
>
> All sorts of neat possibilities. :)
It is truly remarkable the lengths that Perl programmers
Leopold Toetsch <[EMAIL PROTECTED]> wrote:
> Dan Sugalski <[EMAIL PROTECTED]> wrote:
>
> > Okay, okay, I give -- hierarchic namespaces are the way to go. Makes
> > local overrides somewhat interesting, but we'll burn that bridge
when
> > we get to it.
> >
> > find_global P1, ['global', 'name
At 03:05 PM 12/11/2003 -0500, Gordon Henriksen wrote:
Melvin Smith <[EMAIL PROTECTED]> wrote:
> my $foo = Oracle::Instance::DEV1::db_block_buffers;
>
> The namespace lookup in Oracle::Init checks the Oracle config
> parameters which is external code.
>
> All sorts of neat possibilities. :)
It is t
At 9:51 AM -0800 12/11/03, Jeff Clites wrote:
I have some other fixes for this--I'll clean them up and send them
in. I got something working which doesn't crash, and which can find
libraries in standard locations w/o knowing the path. It uses the
native dyld API rather than dlopen--the dlopen wh
Dan Sugalski <[EMAIL PROTECTED]> wrote:
>find_global P1, ['global', 'namespace', 'hierarchy'], "thingname"
> That is, split the namespace path from the name of the thing, and
> make the namespace path a multidimensional key.
> Or I suppose we could just punt and toss the special global acces
I have some other fixes for this--I'll clean them up and send them in.
I got something working which doesn't crash, and which can find
libraries in standard locations w/o knowing the path. It uses the
native dyld API rather than dlopen--the dlopen which shipped with
Panther is just the third-pa
I think a heirarchy is a good idea for namespacing in general. I've
always wanted to be able to tie namespaces in Perl 5. It would only
make sense that if I tie Foo::, that Foo::anything:: would also go
through that tie to get the anything:: stash.
What do you mean by "tie" here? Are you talking
At 11:57 AM 12/11/2003 -0500, Dan Sugalski wrote:
That does, though, argue that we need to revisit the global access
opcodes. If we're going hierarchic, and we want to separate out the name
from the namespace, that would seem to argue that we'd want it to look like:
find_global P1, ['global',
On Dec 10, 2003, at 12:37 AM, Luke Palmer wrote:
Dan Sugalski writes:
At 05:14 PM 12/5/2003 +0100, Leopold Toetsch wrote:
set I2, P1["Foo\x00i"] # I1 == I2
gets currently the attribute idx (0) of "$Foo::i".
Q: Should the assembler mangle the "Foo::i" to "Foo\0i"
I don't like it either, but
Okay, okay, I give -- hierarchic namespaces are the way to go. Makes
local overrides somewhat interesting, but we'll burn that bridge when
we get to it.
That does, though, argue that we need to revisit the global access
opcodes. If we're going hierarchic, and we want to separate out the
name f
If you're on OS X 10.3, I unbroke (sort of) the dynaloading code, so
it now uses the platform dlopen call. This handles .dylib files like,
say, libncurses.dylib. That's good. The bad news, such as it is, is:
*) Still crashes. Ick. a "ulimit -c unlimited" in the terminal will
generate gdb-able c
Bernhard Schmalhofer <[EMAIL PROTECTED]> wrote:
> This patch mostly improves the embedded POD in Getopt_Long.imc and
> getopt_demo.imc.
> There are also some code beautifications, including a s/.pcc_sub/.sub/.
Thanks, applied.
leo
The set_integer_native() vtable method of arrays is implemented
inconsistently. The old historical way in Array was to set an initial
size. My implementation in SArray OTOH only reserves the needed store,
but doesn't change the element count.
new P0, .SArray
set P0, 2
set I0, P0 # SA
I have just installed Fedora Core 1 on a Pentium 4 system, and various
tests are segfaulting when trying to invoke a compiler. I tracked it
down to Parrot_jit_build_call_func. If I undef CAN_BUILD_CALL_FRAMES
then all tests pass. Also, everything segfaults using parrot -j.
uname -a
Linux peter4 2.
20 matches
Mail list logo
