At 05:04 PM 2/17/2003 -0800, Tupshin Harper wrote:
So I'm gonna take a look at the native calling functionality of parrot to
see about access to an XML parser.
Taking a look at the pxs example (is this the right place to be looking?),
and I'm having problems compiling PQt.C per it's own instruc
Tupshin Harper:
# If pxs is truly obsolete, please trash it ;-).
I'm not confident enough about PXS to trash it, but I've commented a few
files appropriately.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
>How do you "test" this 'God' to "prove" it is w
Thank you very much. That example works for me.
One question: What is the preferred way of telling parrot about .so
files like libPQt.so.
Is there some location within the parrot hierarchy where these can be
put to be dynamically found? If not, should there be?
If pxs is truly obsolete, please t
Tupshin Harper wrote:
Taking a look at the pxs example (is this the right place to be
looking?), and I'm having problems compiling PQt.C per it's own
instructions.
I don't know, what's up with pxs, but AFAIK this is obsolete and
replaced by the NCI (native call interface).
Attached is the
