>>>>> "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 nci >> users and that is important IMO. but as i said in my other reply, >> handling hashes is a big issue and that can't deal will all >> possible cases (while you can deal with most of the cases for >> arrays). > Yeah, the hash case is less of a clear win--in addition to the > complexity issues you mentioned, they are also much less used in pure > C code (almost never, really)--since there's no standard hash type in > C, people tend to not write C-based interfaces which use them. 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 wrap this lib in a perl module. if the nci interface can handle describing arguments with their direction (in/out/in-out), sizes, types, etc. and do all the needed work it will make this so much easier. uri -- Uri Guttman ------ [EMAIL PROTECTED] -------- http://www.stemsystems.com --Perl Consulting, Stem Development, Systems Architecture, Design and Coding- Search or Offer Perl Jobs ---------------------------- http://jobs.perl.org
