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 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 pointers. That'd solve my problem quite nicely. But... >> that begs the question--is it going too far? Is this the sort of >> stuff that ought to have custom C interfaces for, rather than adding >> in Yet More Types to the NCI interface? > > 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 something like this in the NCI interface?
Mainly it's two more things for the interface, which grows ever larger. Past that, well... there's no real argument against other than it means more funky assembly code for the JIT building call frames.
If it doesn't slow down the common case, then I'd vote to add it.
Won't make a darned bit of difference for the common case. I think I'm going to go add it, so it's off to hack util.c some, I expect, as it's a bit much to encode completely in assembly of any sort.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
