From: William K. V. <wk...@us...> - 2005-08-01 01:06:52
|
On Sun, 2005-07-31 at 09:59 -0400, Bob Doan wrote: > Right now really only PHP and C are fully supported. (Callbacks, arrays, > ect) ...and python, coming soon ;-) > But for Java,Python,Perl,C# 90% works really well. > > I was hoping to move examples into the wiki for people to learn how to > do things. > > But so far only Carol and I have been doing things in the wiki, so it's > going slow If, as an initial start, you were looking to have the existing documentation imported into the wiki I might have some time next week to start doing that. If you were planning a complete re-write/reorganize/clean-up that is a bit harder. > > Also.. Any luck w/ doing Python callbacks?? I haven't had much time as things have be very busy at work however I am now making pretty good progress. The functionality is almost up to the PHP interface however I've run into what I consider warts on the interface. With PHP you pretty much expect that the program activate, process, and then die with every request so having a lot of globals is kinda normal although that might change with PHP 5. With python using globals is considered poor/lazy/hack programming. The first issue, which can't be worked around if I'm going to get the m.variable idiom to work, is that the "environment" needs to track/store/pass a user variable to all of it's functions. I need this to be able to do reference counting on python objects as well as freeing temporary memory. The second is with the adding of the array datasource. The add_datasource_array call just says I'm going to give you one, the add_query_as passes the name of the array as a string, which is then looked up in the global name space. My thought here would be to deviate from the other implementations and have the add_datasource_array take a reference to the array and then ignore the query string, this allows me to use normal variable scope resolution so the array doesn't have to be global. The problem of course is that deviations cause major confusion when people are trying to port code (humm, now that I think about it I'll have to look at what the C implementation does, I only looked at the PHP one as that seems to be the predominant usage target). Your input on these two issues appreciated. Cheers, William. > On Sat, 2005-07-30 at 19:38 -0600, William K. Volkman wrote: > > I notice that the products.xml file is in the "common" subdirectory > > under examples however the major portion of xml files are located > > in the php subdirectory. Should they move to common or stay where > > they are? |