Dan Sugalski [EMAIL PROTECTED] wrote:
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of ints (and floats, I suppose)
and arrays of char pointers.
Actually we have that already - or almost. When interfacing with PCRE, I
had to access
Dan Sugalski wrote:
At 10:17 AM +0100 12/24/03, Leopold Toetsch wrote:
the UnManagedStruct PMC has an interface to deal with almost arbitrary
structures and arrays of types.
Using the source is only helpful when the docs are sufficient to
actually *find* the thing you're thinking of doing,
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of ints (and floats, I suppose)
and arrays of char pointers. My first thought is to have a new type
that converts an Array (or something like it) to a C array, either of
ints or char
DS == Dan Sugalski [EMAIL PROTECTED] writes:
I'm pondering, once again, more things with the Postgres interface. In
this case I need to pass in arrays of ints (and floats, I suppose) and
arrays of char pointers. My first thought is to have a new type that
converts an Array (or
On Tue, 23 Dec 2003, Dan Sugalski wrote:
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of ints (and floats, I suppose)
and arrays of char pointers. My first thought is to have a new type
that converts an Array (or something like
At 6:07 PM -0500 12/23/03, Simon Glover wrote:
On Tue, 23 Dec 2003, Dan Sugalski wrote:
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of ints (and floats, I suppose)
and arrays of char pointers. My first thought is to have a new type
On Tue, 23 Dec 2003, Dan Sugalski wrote:
At 6:07 PM -0500 12/23/03, Simon Glover wrote:
On Tue, 23 Dec 2003, Dan Sugalski wrote:
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of ints (and floats, I suppose)
and arrays of
DS == Dan Sugalski [EMAIL PROTECTED] writes:
Speaking personally, being able to automatically convert a Parrot array
to an array of ints or floats would be very useful, but that's because I
do fairly hard-core number crunching in my day job. What are the
arguments againtst putting
At 6:45 PM -0500 12/23/03, Simon Glover wrote:
On Tue, 23 Dec 2003, Dan Sugalski wrote:
At 6:07 PM -0500 12/23/03, Simon Glover wrote:
On Tue, 23 Dec 2003, Dan Sugalski wrote:
I'm pondering, once again, more things with the Postgres interface.
In this case I need to pass in arrays of
On Dec 23, 2003, at 4:08 PM, Uri Guttman wrote:
DS == Dan Sugalski [EMAIL PROTECTED] writes:
Speaking personally, being able to automatically convert a Parrot
array
to an array of ints or floats would be very useful, but that's
because I
do fairly hard-core number crunching in my day job. What
JC == Jeff Clites [EMAIL PROTECTED] writes:
On Dec 23, 2003, at 4:08 PM, Uri Guttman wrote:
but it is (just about) one time only work and will save tons of
repeated tricky work down the line for those who will embed c libs
in parrot. the richer this api is, the less problems for the
Uri Guttman writes:
good point. but we definitely would want arrays supported
with all three scalar types and in both directions. in fact, if we just
look at what swig (and other similar projects) is able to do we can make
that stuff easier as well. i recall a minor nightmare when we tried to
12 matches
Mail list logo
