Hi Nicolas, Thank you very much for your kind welcome. Although it should be very easy, I'm still not sure how to get the moose image (I downloaded it) into pharo. should something like: $ pharo moose.image ... work? Or: $ pharo -vm moose.image ... ? I can't find pharo's command line options, although I read the faq and googled a lot. How do I tell it to load the image? Then, how can I 'test' that effectively moose elements are available and ready to be run?

From within pharo, I can't find any 'load image' option. My interest in moose is great. I'm a 25+ years systems programmer, and I have systems written in various languages. I'm sick of duplicated code. I'm tired of lost code because I have to switch the programming language of choice for whatever reason. I want to get real code reengineering into my set of tools, and I came across moose, which as far as I could find out, offers a lot of metrics tools, and also code abstraction, provided you have the proper parsers for your language, and re-write tools in order to really use old but perfectly valid code (which of course can be improved, but starting from a non-nil starting point, or having to reprogram things by hand). I'm doing some of my codebase parsing in python, for convinience reasons, but I can write the same in smalltalk and MSE if I found out that correctly. I've seen that not many people know here about moose, and except a man in my Linux User Group years ago, I've never seen anyone really into smalltak, nor in my university whatsoever. I get annoyed at the lack of attention that things like moose get in my ecosystem/country/zone. So, that's why I'm trying to get ahead and try something new and thoughtful. I'll report back as long as I can 'moose' my codebase and transform it into new languages, which why not, one of them could be smalltalk. I've been in many many different languages before, as you might guess. Maybe the most similar thing to smalltalk that I've seen is common lisp, because of it being a standard, and a live system with a REPL, and with the CLOS. But I've seen nothing like moose in the common lisp world. The software systems that I've wrote for a living, are small-business operations-support, mainly for drugstores/pharmacies in Uruguay. Other systems add up, like CV analysis tools for recruiting, etc. hope that conveys pretty much a part of me and my work. best wishes Haroldo 2013/2/19 Nicolas Anquetil &lt;Nicolas.Anquetil(a)inria.fr <mailto:Nicolas.Anquetil@inria.fr>> Hi Haroldo, welcome to the mailling list and the Moose world. The simplest way to get Moose would be to download it pre-loaded in an image. You can do this from http://www.moosetechnology.org/, there is a button to get the latest image. I you feel like it, later, you could drop a note to say what you were looking for moose in the first place and how you feel about it. It's always nice to have impressions from new members thanks, cheers. nicolas On 02/19/2013 07:07 AM, Haroldo Stenger wrote: -- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

** 1. At http://www.moosetechnology.org/download 2. Download moose 4.7 'moose.zip' file. Unzip this to any folder XXX and you see three files. a. moose.image - is the smalltalk program, including pharo & moose additions b. moose.changes - is like a transaction log - it records changes in method source so that if the image crashes before you save it, you can roll forward changes from the last save. c. moose.st - actually I don't know what this does. I've never had to do anything with it directly. 3. Follow the link through to http://www.pharo-project.org/pharo-download Under 'Virtual Machines' choose Cog-linux.zip - which will download nbcog-linux-latest.zip. This is the CogVM with a few extensions named NativeBoost for calling out to C libraries. Drag the entire contents of the VM zip file into the same XXX folder as the image. 4. From your other Pharo installation, find the PharoV10.sources file and also drop that into the XXX folder. 5. Now on Windows I would just double-click NBCogVM.exe. You should be able to determine what to do on Linux from looking at the Moose.sh file from the Moose-4.6-One-Click. hope that helps smooth the way,

I'm reading the part of the moose book that teaches how to write a parser. I need to write such a parser. I have a system written in a proprietary language, for which there are no external parsers unless I write one. I have a huge file (28MB , 1.5 million lines) which resembles in format a XML file, but it's not really XML, but a variation in tagging program elements. Should I partition the huge file in smaller units before trying to run a MSE parser on it? Or should the huge grammar parser work? I can approach any of the two paths. I think that once everything is inside the meta-model (which I'll have to write too later) , it is of little importance if the data came from a huge file , or if it came from two thousand smaller files. Am I right? How big a model can get? Hope this helps helping me :-) Additionally, the semantics of the proprietary language I'm trying to parse is procedural. It's not object oriented. One of my goals, is to reegineer the procedural code so that it can be abstracted, and made object oriented in some other open source language, like, say, python, or whichever fits. That would involve a 'writer' from the transformations on the model, which is fine. The transformations on the model might rely on some already existent tools in moose, as well as on hand-made tools adapted to the idiosyncracies of this language. I'm looking for general help on this big picture process. I'm willing to deal with the details myself, and ask for help if I get stuck :-) best wishes Haroldo 2013/2/21 Haroldo Stenger &lt;haroldo.stenger(a)gmail.com&gt; hi again ! 2013/2/19 Ben Coman &lt;btc(a)openinworld.com&gt; 1. At http://www.moosetechnology.org/download 2. Download moose 4.7 'moose.zip' file. Unzip this to any folder XXX and you see three files. a. moose.image - is the smalltalk program, including pharo & moose additions b. moose.changes - is like a transaction log - it records changes in method source so that if the image crashes before you save it, you can roll forward changes from the last save. c. moose.st - actually I don't know what this does. I've never had to do anything with it directly. 3. Follow the link through to http://www.pharo-project.org/pharo-download Under 'Virtual Machines' choose Cog-linux.zip - which will download nbcog-linux-latest.zip. This is the CogVM with a few extensions named NativeBoost for calling out to C libraries. Drag the entire contents of the VM zip file into the same XXX folder as the image. 4. From your other Pharo installation, find the PharoV10.sources file and also drop that into the XXX folder. 5. Now on Windows I would just double-click NBCogVM.exe. You should be able to determine what to do on Linux from looking at the Moose.sh file from the Moose-4.6-One-Click. hope that helps smooth the way, I'm running moose ! I'm happy I could reach this point. Your tutorial works great. Now I'll need to grasp the basics in here. I'll be googling and navigating the moose site. Anyway, would you like to further soomth my way , feel free to :-) thank you very much Haroldo _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev

> hi! > > I'm totally new to smalltalk, although I've heard of it since a lot of time ago.

> In my arch linux installation, I've found some dificulties running squeak, so I went into pharo once I've discovered they are two free implementations of smalltalk. > > Then I wondered myself, How can I do now to put moose into here ? And then I saw that by selecting the proper text in one of the default windows that pharo opens for me, I could have moose (and other subsystems) installed in the image I'm workin on. So I did. > > I've found myself pretty impressed at the ease by which the subsystems get installed. I started installing one of the web development systems, and I got thru the whole automated process without any problems. > > Then I evaluated the code that installs moose. It started running, and run a lot without a problem too. But at some point, some missing methods poped up a window in which I'm asked what to do.

> At the firsts of them, I put 'proceed' (because I wouldn't abandon, nor debug because I woudn't know what to do), and it proceeded. At some later pop up errors, I was offered a fourth option namely 'create', I did, and put the method I was asked to put somewhere in systembase or some similar name (I can be more precise if needed or asked to), then a code that showed a 'to be implemented' dummy method or something, and then again, asked to proceed, and and did this process a number of times, until I realized that there were many of them, and I abadoned. And went here, asking for some kind help of you.

> > I could insist with squeak if that would do better, or go Cuis alternatively (but from what I've read, maybe Cuis would not fit).

> I've also read that pharo support from moose is in some development phase. Is that true?

> So if I'm a beginner I should try it until it's ready. > > I'm interested in moose mainly, and derived from this, in smalltalk and in any of its free versions if they work.

> Any hint is welcome.

-- Nicolas Anquetil -- RMod research team (Inria) _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev