Neil Madden <nem00u / cs.nott.ac.uk> writes:

> Donal K. Fellows wrote:
> 
> <snip interesting discussion, which mostly goes over my head :>
> 
> > 
> > BTW, how does Parrot handle calls to foreign code?  The docs I've seen are on
> > the hazy side, and integration with existing C, C++ and FORTRAN monoliths is
> > (alas) all too important in particularly commercial development.
> > 
> 
> On this particular point; has anyone thought of writing a unified C-API for Tcl, 
> Perl, Python, Ruby, (Java) etc? What I mean by this is that each of these 
> languages can be extended in C, and quite often are. Also, whenever I see 
> interesting new C/C++ libraries implemented, I also tend to see seperate 
> language bindings for each of these languages. This seems like a massive 
> duplication of effort. Would it be possible to abstract over the C API's of 
> these languages to a common core of functionality which all share (e.g. getting 
> an interpreter handle, registering a command, setting a variable etc)? I have 
> only dealt with Tcl's C interface, so this may be too difficult, but it seems 
> like it would be a huge step forward.

Look at
	http://www.swig.org/

Regards,
	Slaven

-- 
Slaven Rezic - slaven.rezic / berlin.de
Tired of using file selectors? Real programmers use the TAB key for
completion and not for jumping around. Try
	http://search.cpan.org/search?mode=module&query=Tk::PathEntry