Christopher Hicks writes: >On Tue, 3 Aug 2004, Sam Holden wrote: [snip] > >> There are two Wily modules in existance at the moment (that I know of), >> but they do the same thing - one uses XS to link with the wily libs, >> whereas mine uses pack/unpack to decode the messages itself. But yes, >> there's much less scope for multiple modules (due to the fact that the >> intersection of wily users and perl programmers is small...) > >How about TextEditor::WilyPP. Is PP recognized as pure perl widely >enough? If the XS-based module owner could be convinced to switch to >TextEditor::Wily you'd really be starting a trend.
I'd be more inclined to modify the existing XS module and my non-XS module to have the same interface. Currently you could replace my Wily::Message and Wily::RPC modules with XS modules easily enough (since they are simply perlifications of the msg.c and rpc.c code from Wily - well actually they are perlifications of the pythonifications of that code - which actually made it too OO for my perl tastes, but it was quicker to code). That way the same Wily.pm wrapper could be used to give a "nicer" (of course that term is very subjective) interface to both versions of the code. A little like Text::CSV_XS and Text::CSV (though I don't know if they have the same interface, it's just one case I know of where an XS version and a non-XS version exist). Of course in that case performance might actually matter, I doubt it ever will when interfacing to a text editor with a message-response interface over a unix domain socket. I don't think the XS code is on CPAN anyway, the author is on the wilyfans mailing list though so I'm sure something could be arranged. Anyway TextEditor::Wily seems like a reasonable thing to try, so unless there are any obvious problems with that I'll ask for it tomorrow. -- Sam
