Stéphane Ducasse wrote:
I shoud say that I do not really understand the goal of what you are doing. Using Famix for code generation? representing parser results? I have the impression that when you have a boolean and the parser give you nil then you know that this is not the value but unknown. May be this is what you do not like doru (I got confused). But the isKnown was the solution to this problem at that ancient time :)
Stef
Mmmmh... I can't say that I really like the "isKnown" solution.
The idea of our talk (at least my side) is that if default values -are- primitive values; we might as well include them in the FAMIX.fm3.mse specification. This would allow code generation in different platforms to actually write the correct initialization for those values. And then famix-files would be allowed to omit values which are the default ones. As we saw for famix specified in fm3 where we specified default values (Adrian got a bit mixed up and reused these default values also for other metamodels); this shortens the length of some files quite a lot. (and reduces the time needed for parsing and initializing obviously...)
Toon