Re: VB language extensions wishlist

On Feb 17, 8:43 am, "Schmidt" <s...@xxxxxxxxx> wrote:

Would appreciate it, if we could end up with a true, machine-
code-emitting compiler, able to link BreakPoints to
Basic-Code.

FreeBASIC is moving to using the backend the GCC compiler which is
somewhat language neutral. So FreeBASIC doesn't emit C++ code but
rather whatever intermediate codes/files needed by the GCC backend.

It has a downside in that "new" side of FreeBASIC reflects the
capabilities and limitations of the backend. For example the new
FreeBASIC doesn't have GOSUB RETURN. FreeBASIC preserve QuickBASIC
compatibility via a flag -lang qb and you get the ability to use
GOSUB..RETURN but not the new stuff. I advice checking out the forums.

The thing with the MONO runtime is that it may be easier to adapt that
to COM than with the GCC Backend. While .NET isn't backwards
compatible it not that different than how COM does things. Plus using
the MONO runtime will allow the option to ignore the limitations of
COM if a programmers decides to do so.






.

Relevant Pages

  • Re: Why?
    ... There is still active work on CM3/PM3 ongoing; ... distribution quite some time ago; ... and that it's not a standard backend for GCC means that it "falls just short" ...
    (comp.lang.modula3)
  • Re: Why?
    ... a single-standard based on GCC4 with intent to make the backend part of GCC. ...
    (comp.lang.modula3)
  • RE: libstdc++ writev/2.04/patches upstream?
    ... gcc is slow as in gcc is slow on Linux/Unix. ... And, then, likely also a factor, perf of: ... Ok, DosBox isn't very interesting/relevant, ... The C front end is c1.dll, C++ c1xx.dll, the backend c2.dll. ...
    (comp.os.msdos.djgpp)
  • Re: Possibly fixed in gcc 4.1.1, but bug box -- Was: Re: A smaller self contained test case
    ... it, this means that the gcc version, even if GMGPL, can be in any state. ... heavy changes due to the addition of 2005 features, ... GNAT Pro and GNAT GPL still use the 3.4.6 backend. ...
    (comp.lang.ada)