On 2/28/07, Marvin Humphrey <[EMAIL PROTECTED]> wrote:
On Feb 27, 2007, at 5:44 AM, howard chen wrote: > Hello, > > I know that Lucy planned to support Perl & Ruby but still in a very > early stage. > > Anyway, If I am going to implmenet a blinding for PHP, what should I > know or need to prepare? > > Is it still early to ask this question? It's still a bit early, but stick around. A couple of days ago, I managed to get the first dev release of KinoSearch 0.20 (0.20_01) out the door. A lot of the work that has gone into it was informed by discussions here; the new version is considerably closer to Ferret and to the theoretical "Lucy" than the current KS release, 0.15. One thing we're going to need is a way of communicating to bindings authors what is and isn't public API.
How about just using doxygen. I don't have much experience with it but I'm pretty sure there would be a way to tag particular functions that are public so that when you generate the documentation you can generate only the public methods. Of course you could also have public and private include files.
I'm thinking we need shared documentation. XML, maybe? Then each binding would require an appropriate XML-to-whatever translation utility.
I'm not entirely sure I'm on the same wavelength as you today. By 'whatever' do you mean the specific languages documentation format? If that is the case then I don't see this working as the ruby API for Lucy will probably be quite different to the PHP API. But, maybe you're talking about something completely different. Cheers, Dave -- Dave Balmain http://www.davebalmain.com/
