Re: Any interest in an HTML DOM in C / C# / similar? (was Re: State of the AJAX Union)

For one particular application, I need the speed of Perl's regex engine and
I have not been able to match it in C# or even with limited attempts using
C++ and Boost's regex library.  So, regardless of feature availability on
other platforms, I'm going to continue pursuing DOM & JS functionality in
Perl extending WWW::Mechanize.

That said, I do a lot of *other* work in C# and what you suggest would be
useful.  If you already have something in the works (you mentioned
publishing some code), I'd be interested in learning more.

On 11/23/06, John J Lee <[email protected]> wrote:
>
> On Wed, 22 Nov 2006, Christopher Hart wrote:
>
> > Would an "easier" (yet still monumental) starting point be to tackle the
> DOM
> > implementation independent of a JS engine?
> [...]
> > This seems like a great open source project - it's way too much to
> handle
> > for most individual developers, but I think could be tackled with a
> > moderately organized team of folks with a good design laid out in
> advance.
> [...]
>
> So, having pooh-poohed Christopher's proposal, I'm going to make a very
> similar proposal of my own.
>
> Give me some slack, I have the excuse of actually having put in some
> implementation effort on this, and published the code :-) (but not in
> Perl).  And I'm asking with a view to writing some more code myself
> (albeit only a slim chance of that happening).
>
> So, my question / semi-serious proposal is: is anybody here interested in
> collaborating in writing a portable HTML DOM library and DOM builder in a
> language *other* than Perl, with the intent of wrapping it for Perl and
> other languages (Python is my own interest)?
>
> I'm afraid I'm not interested in Perl 6's cross-language support, though.
> If it were me working on it, it would probably have to be C, C++ or C# (or
> possibly Java, or something weirder like Caml).  Cross-language use is one
> reason for my thinking about doing it in one of those languages.  Memory
> usage and execution speed is another.  I lean towards C or C#.
>
>
> John
>
>