Le 26/07/2014 12:12, kilon alios a ��crit��:
there Shampoo already

http://dmitrymatveev.co.uk/shampoo/
Didn't know about that one. Looks good :)

or do you mean something different ?
Yes. A true, single source approach. Smalltalk as 10 000 - 100 000 lines of code in a single file. People recompiling a complete package each time they change a method.

The real programming world, good to sell to companies :)

We also need to look into making Smalltalk less efficient at code reuse. It's possible to write far too effective code in very few lines. Like that we would be able to increase our GitHub presence.

Thierry




On Sat, Jul 26, 2014 at 1:04 PM, Thierry Goubier <thierry.goubier@gmail.com> wrote:
Le 26/07/2014 10:04, Marcus Denker a ��crit :

On 26 Jul 2014, at 10:02, stepharo <stepharo@free.fr> wrote:

Thierry we asked Mark Rizun to look into get a full "compilation unit" as an AST:
�� �� - AST for packages
�� �� - AST for class definition.
He should look at what gisela proposed and any feedback is interesting.

Only the name AST is wrong: the S stand for Syntax. There is no syntax for Classes, nor
packages.
We could have one. It would allow people to write Pharo code with emacs, have a pharo emacs-el mode, and try a different way to use git :)


What we want is models for everything with *the same API* as the nodes of the AST.
(and visitors that can visit the whole structure)
This would be cool. I have the nodes and the visitors for all the way from packages to method, but it stops at the method / class description level (and switches to the RB ast then).

Thierry