[gobo-eiffel-develop] Git development

[Howard T. <how...@di...>]

Hi Eric & Wolfgang,

I would welcome a move to using Git as the SCM system for Gobo.

I see that there is a useful page on wikipedia about git, with reference to Windows implementations:

http://en.wikipedia.org/wiki/Git_(software)#Implementation

There is also an excellent website detailing how to use git ...

http://progit.org/

Regarding my own project:

I have recently, I think [famous last words], reached stability with my
GC when compiling with my modified 'gec', albeit that I have only so
far tested it on Linux. A Win32 version should be a fairly trivial adaptation,
as it should be no more than adaptation of a single, smallish, routine.

I am also thinking of renaming my project as 'guide',
the Gobo-eiffel Users' Integrated Development Environment,
from 'edp', the Eiffel Developers' Project. Although there a few
classes [from other sources] that are LGPL, nearly all code that does
not already derive from gobo, is EFFLv2 or MIT.

I am very interested to hear about the introspection and debugger code, as
I need such facilities for my intended future coding.

One of the areas of the code generator that I intend to alter is the polymorphic
dispatch implementation, for two reasons:

Firstly for rapid re-compilation, I want to be able to generate an initial code package as
an executable stub with dynamic library, where libraries register their routine addresses
with the runtime, with subsequent partial re-compilation code generated as an additional
dynamic library whose routines override the registered routines of the initial library. This
requires that routine dispatch be done using a tree data structure, of some sort ...

Secondly, I envisage that it should be possible, as with Java and other languages [mostly interpreted ..],
to dynamically add class libraries to an executable system, where such libraries have been packaged,
[compiled or otherwise verified against] to be compatible with classes already in the current system.
That would also require that the dispatch to reachable routines be dynamically extendable.

I am adapting my work on the Eiffel GUI toolkit derived from the Fox-toolkit to use the Vision2 interface,
providing an X11/Win32 all Eiffel GUI Toolkit, which has its advantages ...

I am working toward using LLVM as the basis for code generation for native Eiffel routines, initially to emit
LLVM assembler with llvm-as invocation, and with the possibility [much] later of emitting machine code directly.

I think using Git would assist in cooperation between myself and other gobo-eiffel contributors and developers.

Regards,

Howard Thomson

--
"Only two things are infinite, the universe and human stupidity,
and I'm not sure about the former." -- Albert Einstein