I've been using RB, which allows to recreate on demand the ast, but in
my system i cached those values.
ast := RBParser parseMethod: 'parsingAMethod
| yeah |
yeah := self doesAMethodNode rememberitssource.
yeah
ifTrue:[ ^ #hurray]'.
On Aug 16, 2012, at 9:32 AM, Fernando Olivero fernando.oliv...@usi.ch wrote:
I've been using RB, which allows to recreate on demand the ast, but in
my system i cached those values.
ast := RBParser parseMethod: 'parsingAMethod
| yeah |
yeah := self doesAMethodNode remember
Mariano,
This is the same problem that occurred when the first code using
ZnSignalProgress was integrated in Pharo 2.0, it failed the first time only. I
just can't remember how we got past this, I guess by a manual intervention by
one of the integrators. I could also be that Sean committed
NICE! I would say lets go for it, 120MB is nothing nowadays. The IDE
could be simplied and be more powerful.
For example, in gaucho i'm using the ast for pretty printing of the
source, and for styling unsed variables differently, etc...
Fernando
On Thu, Aug 16, 2012 at 9:35 AM, Marcus Denker
On Aug 16, 2012, at 4:05 PM, Fernando Olivero fernando.oliv...@usi.ch wrote:
NICE! I would say lets go for it, 120MB is nothing nowadays. The IDE
could be simplied and be more powerful.
it kind of changes quite drasitically what you can do concerning behavioral
reflection...
As for space,
On 2012-08-16, at 16:17, Marcus Denker marcus.den...@inria.fr wrote:
On Aug 16, 2012, at 4:05 PM, Fernando Olivero fernando.oliv...@usi.ch wrote:
NICE! I would say lets go for it, 120MB is nothing nowadays. The IDE
could be simplied and be more powerful.
it kind of changes quite
On Thu, 16 Aug 2012, Fernando Olivero wrote:
NICE! I would say lets go for it, 120MB is nothing nowadays. The IDE
could be simplied and be more powerful.
Let's be a bit more realistic. The current garbage collector is choking if
you add 100 MB of small objects to your image. Caching the
14458
-
Issue 6555: DNU on ctrl home / ctrl end
http://code.google.com/p/pharo/issues/detail?id=6555
Yes, caching is what i do in my system. It would amazing that Pharo
implements such a caching scheme for methods and their ast .
If you evaluate the code i pasted before, you will note that it does
preserve the actual source.
RBMethodNodesource
^ source
instead, RBMethodNodeformtattedSource ,
I read a paper once (at the University of New Brunswick (Canada))
library in which the grammar for a language was used to construct a
data compressor for syntaxly correct programs. The output was a
compressed form of a parse/syntax tree with comments and white space
included. Once decompressed,
On Aug 16, 2012, at 6:13 PM, Ralph Boland wrote:
I read a paper once (at the University of New Brunswick (Canada))
library in which the grammar for a language was used to construct a
data compressor for syntaxly correct programs. The output was a
compressed form of a parse/syntax tree with
On 16 Aug 2012, at 19:29, Stéphane Ducasse wrote:
On Aug 16, 2012, at 6:13 PM, Ralph Boland wrote:
I read a paper once (at the University of New Brunswick (Canada))
library in which the grammar for a language was used to construct a
data compressor for syntaxly correct programs. The
I read a paper once (at the University of New Brunswick (Canada))
library in which the grammar for a language was used to construct a
data compressor for syntaxly correct programs. The output was a
compressed form of a parse/syntax tree with comments and white space
included. Once
Sven Van Caekenberghe wrote
I could also be that Sean committed something.
I'll take a look tomorrow at the latest. If it's an emergency, I might be
able to check later tonight...
--
View this message in context:
14 matches
Mail list logo
