Re: [gobo-eiffel-develop] GEC introspection & debugger

[Wolfgang J. <wj...@so...>]

Eric Bezault wrote:
> Wolfgang Jansen wrote:
>
>> Of course, the reason is the typesets, but the effect is the false 
>> void check.
>
> I understand that. What I'm saying is that the false void check
> is just the top of the iceberg. It is a particular case of a
> more general issue that will also occur with dynamic binding,
> even though you only saw it with void checking so far. This is
> a known issue with the dynamic type set builder that also occurs
> with 'external "C"' functions when the returned object has been
> created in C. What I was trying to say is that the solution is
> not to try to fix the Void checking, but the more general
> problem with the dynamic type set builder. Otherwise there will
> still be problems with the dynamic binding, even though you
> didn't see it yet.
I was already concerned with the problem of creating Eiffel objects in C.
I hoped that dynamic binding is not a problem:
if an XYZ object is accepted as such (i.e. no false void check)
then the dynamic dispatch on the object will work as if the object
had been created in Eiffel (i.e. calling the same T123x456 functions).
Isn't so? The objects created in C or read from a store file do not
introduce new inheritance relations. (If they were created before storing
by a system having different inheritance relations then these relations
are not part of the store file, and after retrieval the objects have
to be treated as objects of the retrieving system.)

> There was no misunderstanding. The "normal" compilation uses
> ET_AST_FACTORY. It should be told to use ET_DECORATED_AST_FACTORY
> when you want to use it as part of a debugging compilation.
>
OK, so I will modify the parsing or analysis part of the compiler
(I tried to avoid those modifications to maintain compiler consistence).

On hour later: I changed the type of ET_TOKEN_CONSTANTS.default_ast_factory
from ET_AST_FACTORY to ET_DECORATED_AST_FACTORY
but the position of some ET_KEYWORDs is still zero
(I had a look only on the `rescue' keyword).
>
> I'm currently looking at the possibilities to host the Gobo
> repository under git.
>
I did not yet use git, I just read the manual.
It looks promising but I do not see the big step forward.

-- 
Dr. Wolfgang Jansen
University of Potsdam, Germany
Institute of Computer Science
Tel: +49 331 / 977 3047
mailto: wj...@so...