"No, they tried and died."
Ok, it's not that bad, but it doesn't seem to work. I moved the .pmcs (same files in previous attachment) over to ./dnyclasses, updated the Makefile as directed in dynclasses/README.
To undo their previous inclusion, I did a make realclean, config, and make.
After that, I see the following behavior:
bash-2.05a$ ./parrot dynclasses/dynfoo.pasm
open result was Access (5) for filename [foo]
open result was Access (5) for filename [foo.dylib]
open result was Access (5) for filename [foo]
open result was Access (5) for filename [foo.dylib]
ok 1
54
ok 2
42
bash-2.05a$ cat joe.imc
.sub main
$P1 = loadlib "tclstring"
end
.end
bash-2.05a$ ./parrot joe.imc
open result was Access (5) for filename [tclstring]
open result was Access (5) for filename [tclstring.dylib]
open result was Access (5) for filename [runtime/parrot/dynext/tclstring]
Couldn't load 'runtime/parrot/dynext/tclstring': unknow reason
open result was Access (5) for filename [tclstring]
open result was Access (5) for filename [tclstring.dylib]
open result was Access (5) for filename [runtime/parrot/dynext/tclstring]
Couldn't load 'runtime/parrot/dynext/tclstring': unknow reason
So... it's finding the lib (finally) at "runtime/parrot/dynext/tclstring.dylib" - but couldn't load it. The foo load seems to work fine, though.
What next?
And, are we going to move Perl* pmcs into dynclasses? I'd hate for them to bloat my parrot executable when running Tcl. =-)
On Friday, April 9, 2004, at 03:39 AM, Leopold Toetsch wrote:
Will Coleda <[EMAIL PROTECTED]> wrote:--
Attached, find a .tgz that can be exploded in the top level of parrot which creates the abstract pmc "tclobject", with children "TclString", "TclInt", "TclFloat", and container pmcs "TclList" (an array) and "TclArray" (a hash).
Can we put these PMCs into dynclasses? I don't think that Parrot core
should contain all possible PMCs of all supported languages. OTOH we
should have some support for selecting $LANG PMCs at compile time (and
no, I don't cosider the current manual selection of classes as support:)
A re-configure/make is necessary to be able to use the Tcl* pmcs if you're feeling adventurous.
Can you try it with dynclasses?
leo
Will "Coke" Coleda will at coleda dot com
