Re: New assembly language instructions to support OO languages?

Jasen Betts <jasen@xnet.co.nz>
11 Dec 2008 10:52:32 GMT

          From comp.compilers

Related articles
[28 earlier articles]
Re: New assembly language instructions to support OO languages? cfc@shell01.TheWorld.com (Chris F Clark) (2008-12-08)
Re: New assembly language instructions to support OO languages? gneuner2@comcast.net (George Neuner) (2008-12-09)
Re: New assembly language instructions to support OO languages? jasen@xnet.co.nz (Jasen Betts) (2008-12-09)
Re: New assembly language instructions to support OO languages? efeustel@hughes.net (Edward Feustel) (2008-12-09)
Re: New assembly language instructions to support OO languages? gah@ugcs.caltech.edu (Glen Herrmannsfeldt) (2008-12-09)
Re: New assembly language instructions to support OO languages? kamalpr@hp.com (kamal) (2008-12-10)
Re: New assembly language instructions to support OO languages? jasen@xnet.co.nz (Jasen Betts) (2008-12-11)
Re: New assembly language instructions to support OO languages? first@last.name (Morten Reistad) (2008-12-12)
Re: New assembly language instructions to support OO languages? torbenm@pc-003.diku.dk (2008-12-12)
Re: New assembly language instructions to support OO languages? johnzabroski@gmail.com (John \Z-Bo\Zabroski) (2008-12-13)
Re: New assembly language instructions to support OO languages? bear@sonic.net (Ray Dillinger) (2008-12-13)
Re: New assembly language instructions to support OO languages? jasen@xnet.co.nz (Jasen Betts) (2008-12-14)
Re: New assembly language instructions to support OO languages? gavin@allegro.com (2008-12-16)
| List of all articles for this month |
From: Jasen Betts <jasen@xnet.co.nz>
Newsgroups: comp.arch,comp.compilers
Date: 11 Dec 2008 10:52:32 GMT
Organization: Dis (not Dat) Organisation
References: 08-12-042 08-12-045 08-12-055
Keywords: architecture, design
Posted-Date: 11 Dec 2008 07:55:30 EST

On 2008-12-09, George Neuner <gneuner2@comcast.net> wrote:


> I _think_ if implemented right, it could have been 99% backward
> compatible while requiring no application or compiler changes. The
> only sticky problems I can think of offhand are callbacks (mentioned
> already) and direct access by the application to DLL data (I don't
> know how often that is done in practice). API controlled data access
> would be no problem.


any DLL that has a function that returns a constant string
(eg: version string, error message, or copyright message)


like wheel jacks common but infequently used.



Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.