Replies: 2 comments
-
|
Hi, There was VerveineC that was the start of a C parser but the support got dropped over the years. A C parser was started here: https://github.com/moosetechnology/Famix-C-Importer I think it is still in progress but @NicolasAnquetil can probably tell you more on the status after the holidays |
Beta Was this translation helpful? Give feedback.
-
|
To build a Moose image you just need to get it from the Pharo Launcher as described in the README of https://github.com/moosetechnology/MooseIDE. Moose itself is independent of the programming language being analyzed. Be aware however that there is no parser available for C++. We currently only parse C files. There are still some corner cases that the parser cannot parse correctly, but it is already usable |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Despite my rather thin experience with Pharo, I came across the existence of Moose and thought it would be a great tool to extract the code structures of our heavy C/C++ code bases.
With this hope in mind, I engaged in the project of building an appropriate Moose image with the goal of having the complete tool for this large analysis.
I've tried to follow the several tutors available on the ModularMoose blog, themoosebook, and GitHub, including Famix, tree-sitter, and its C and C++ libraries.
But I'm still struggling to build a functioning Moose image, and it has become so big that during the last loading attempt, it crashed my laptop.
At the current point I've reached, the Moose image doesn't yet deliver the expected result of producing the graphical synthesis I was expecting.
I probably followed a misleading track.
All this introduction is to explain why I'm asking for some help:
In both cases, some more documentation to efficiently exploit the Moose image would also be of really valuable help.
Thanks in advance for any help.
Beta Was this translation helpful? Give feedback.
All reactions