21 Sep
2008
21 Sep
'08
12:44 p.m.
Yes exactly and I would like to use the importingContext of specify
how to filter
the model but in a conistent manner.
Stef
On Sep 21, 2008, at 11:33 AM, Oscar Nierstrasz wrote:
Well, if a visitor has to implement many visit methods, but not all
visitors need to do something for visitable items, then it is handy to
have a default visitor that implements all the visit methods with
empty bodies. You then simply subclass this default visitor and
override the few visit methods that you need.
There is an example in the compiler construction course.
https://www.iam.unibe.ch/scg/svn_repos/Lectures/CompilerConstruction/04Pars…
https://www.iam.unibe.ch/scg/svn_repos/Lectures/CompilerConstruction/Exampl…
Cheers,
- on
On Sep 20, 2008, at 23:33, Tudor Girba wrote:
I am curious about the use case. Could you
elaborate a bit on this
one?
Cheers,
Doru
On Sep 18, 2008, at 1:18 PM, Oscar Nierstrasz wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I guess you mean a default visitor with empty visit methods that can
be subclassed?
Yeah, we need that.
- on
On Sep 18, 2008, at 13:09, stéphane ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi guys
We are looking for a model walker (visitor).
Does any one of you already implement one?
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)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