The more importers we have, the better it is.
To get it into Moose, the first thing would be to create a
CAnalyzerLoader class that works like the Moose or Mondrian one. Like
this, we can manage the tree of dependencies in Moose.
However, there are several problems/issues:
- It depends on Rio, and Rio introduces the ugly bug that freezes the
image when switched from Mac to Windows. Until this is solved (either
by removing Rio or making it not to freeze) we should not include it
- It is not loadable in the current Moose due to missing classes. I
guess this is easily solvable
- What are the dependencies to the external parser? Could we get these
sources in the image and install them on the fly? Or should we add
these sources in the .app?
In any case, I added a page on the moose website:
On 25 Aug 2009, at 17:49, Alexandre Bergel wrote:
'java4Moose' should be removed. It does not make sense anymore.
I create an entry CAnalyzer in http://moose.unibe.ch/tools
On 25 Aug 2009, at 11:40, Simon Denier wrote:
> On 25 août 09, at 17:31, Alexandre Bergel wrote:
>> Dear All,
>> Over the last months, I worked on CAnalyzer, an extension to FAMIX
>> to cope with C. I think it is mature enough to be part of the
>> Moose release.
>> In VW, the Moose distribution was an aggregation of tools.
>> Installing Moose installed all functional tools.
>> I think we should have a similar setting for the Pharo version of
>> Shall I augment MooseLoader with CAnalyzer?
> I see no problem with that. Perhaps it would be good also to sync
> the website.
>> Alexandre Bergel http://www.bergel.eu
>> Moose-dev mailing list
> Moose-dev mailing list
Alexandre Bergel http://www.bergel.eu
Moose-dev mailing list
"Next time you see your life passing by, say 'hi' and get to know her."