On Jan 4, 2013, at 9:56 AM, Igor Stasenko <siguctua@gmail.com> wrote:
On 4 January 2013 09:51, Torsten Bergmann <astares@gmx.de> wrote:
yes it needs sources (indirectly) to bind method's argument names during code generation.
Sad. So this is currently a showstopper in using NB in deployments where one would not like to give the sources away.
If we want (commercial) developers to write applications in Pharo there should be a fix for that.
Yes. I don't like it either. It needs only the arg names (and their order) and for that, it involves a compiler to parse source and generate AST. Which can be completely avoided if temp names is stored somewhere after compilation.
We need a higher level model of code then what CompiledMethods can give us. There is always the question if now, where even a $25 computer has 256MB of RAM, one should not revisit the design decisions that people took in the 30 or even 40 years ago... Marcus