Eric Bezault
Eric Bezault
> Basically what I mean is the GOBO external C impl structure better to match ISE external C impl structure, so no link surprise. Yes, so they are macros in...
In other worlds, the `eif_*.h` files are a bridge between the Gobo Eiffel runtime and what is expected to compile ISE's libraries.
I provide them as needed. Sometimes they don't end up in the right `eif_*.h` file my assumption was wrong (they were added here because it allowed one ISE library to...
I figured out what is the equivalent of `eif_id_object` in Gobo. So I will be able to provide a fix.
I cannot accept this pull request as it is. Too many issues to report them one by one in the PR. In summary: * The description of the class mentions...
> Another thing I want to discuss beforehand is: do your really think the use of Python is a concern? During the past almost 30 years, I received many contributions...
> > `is` keyword is deprecated > > This is to make the code can be tested with the last ECMA compliant SmartEiffel compiler. I don't think we should care...
This needs to be double-checked in the code, but if I recall correctly you have to look at `first_precursor` and `other_precursors`. If they are not Void, then see whether their...
I think it would work, except that ET_INHERITED_FEATURE objects are intermediate objects only used in the feature flattener. They are not kept in the AST objects. So with the former...
Simplest way is the former solution: no need to modify Gobo's code, so no risk to break it. Just call the Gobo code from your code to generate the AST,...