Hi Fabrizio,
I think you have two strategies:
1. Build the importer in VA and export MSE This is way we are dealing with VW: use the importer in VW and export the MSE file. This was because we already had the importer and FAMIX in VW.
2. Build a dedicated Parser and importer As you suggested, you could build a parser. I guess that the syntax is not (much) different. In this case, I would build a surrounding parser that deals with the specifics of the .st file and uses PPSmalltalkParser for the actual method parsing. Given that the Pharo importer already uses the RB AST, perhaps you can directly make the parser to instantiate RB AST nodes.
I would rather favor the second option. If we go in this direction, we could also make it so that the Smalltalk importing infrastructure is flexible enough to only require different parsers.
Cheers, Doru
On Wed, Feb 20, 2013 at 1:01 PM, Fabrizio Perin fabrizio.perin@gmail.comwrote:
Hi, I would like to create a Moose model of a VisualAge smalltalk application. I tried to fileout a bunch of applications (which are groups of packages as far as I understood) and the result file .app has naturally a different syntax from pharo st files. Now, the questions are:
- Should I customize the PPSmalltalkParser or should I start a parser
from scratch?
- Did anybody tried to import in moose a smalltalk dilect different
from pharo? If yes how did he do that?
I just want to understand if I can save time or I should build a whole parser and importer from scratch.
Thanks for any suggestion or information.
Cheers, Fabriyio (bloodz german kezboard) _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev