[Pharo-project] CAnalyer

Schwab,Wilhelm K bschwab at anest.ufl.edu
Sat Sep 26 00:38:29 EDT 2009


Sig,

Is it something you have made available?  One snag in my world is that the "code" is not always something that can be compiled.  However, for GSL and other libraries of interest, the code is valid, if not full of macro-based annoyances and other distractions.

Bill


-----Original Message-----
From: pharo-project-bounces at lists.gforge.inria.fr [mailto:pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Igor Stasenko
Sent: Friday, September 25, 2009 11:03 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] CAnalyer

2009/9/26 Schwab,Wilhelm K <bschwab at anest.ufl.edu>:
> I was digging around on Squeak Source for OSProcess and friends, and ran across CAnalyzer.  Are there any papers on it?  How robust is it?  What does it extract from C code?  For example, might one put the GSL (www.gnu.org/software/gsl) header files into it, pull out all of the structure definitions and function prototypes, and generate LOTS of FFI code to make a wrapper?  Just a thought...
>

I having a modified version of SWIG, which can parse C++ files, including classes and nested classes, to produce smalltalk code wrappers.

Reproducing the SWIG in smalltalk would be very time consuming.
But it would be cool to have a C/C++ parser implementation.

SWIG is not only parsing, its also doing macro preprocessing, so its can't be fooled with macros :)

> Bill
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project at lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
Pharo-project at lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project



More information about the Pharo-dev mailing list