From: ········@hotmail.com
Subject: OMG approves IDL mapping to Common Lisp
Date: 
Message-ID: <87sqjb$4a3$1@nnrp1.deja.com>
Hey, all, I just received an email from www.franz.com:  the OMG has
approved their proposed IDL mapping for Common Lisp.  The document is
available from
http://www.omg.org/techprocess/meetings/schedule/techtab.html#lispmap.

Sincerely,
Douglas M. Auclair


Sent via Deja.com http://www.deja.com/
Before you buy.

From: Fernando D. Mato Mira
Subject: Re: OMG approves IDL mapping to Common Lisp
Date: 
Message-ID: <38A28AA3.EEF109E4@iname.com>
········@hotmail.com wrote:

> Hey, all, I just received an email from www.franz.com:  the OMG has
> approved their proposed IDL mapping for Common Lisp.  The document is
> available from
> http://www.omg.org/techprocess/meetings/schedule/techtab.html#lispmap.

Well, Bill Janssen cried for help in 1998, but I never saw the OMG post
an RFC here.

--
Fernando D. Mato Mira
Real-Time SW Eng & Networking
Advanced Systems Engineering Division
CSEM
Jaquet-Droz 1                   email: matomira AT acm DOT org
CH-2007 Neuchatel                 tel:       +41 (32) 720-5157
Switzerland                       FAX:       +41 (32) 720-5720

www.csem.ch      www.vrai.com     ligwww.epfl.ch/matomira.html
From: Joachim Achtzehnter
Subject: Re: OMG approves IDL mapping to Common Lisp
Date: 
Message-ID: <x5k8kcbk5q.fsf@soft.mercury.bc.ca>
"Fernando D. Mato Mira" <········@iname.com> writes:
> 
> I never saw the OMG post an RFC here.

The OMG Web site has detailed information about the processes they use
to develop OMG standards. These procedures do not include a public RFC
process, generally only OMG members can actively participate in the
standardization process.

Joachim

-- 
·······@kraut.bc.ca      (http://www.kraut.bc.ca)
·······@mercury.bc.ca    (http://www.mercury.bc.ca)
From: Fernando D. Mato Mira
Subject: Re: OMG approves IDL mapping to Common Lisp
Date: 
Message-ID: <38A3EA3A.2367E1C2@iname.com>
Joachim Achtzehnter wrote:

> "Fernando D. Mato Mira" <········@iname.com> writes:
> >
> > I never saw the OMG post an RFC here.
>
> The OMG Web site has detailed information about the processes they use
> to develop OMG standards. These procedures do not include a public RFC
> process, generally only OMG members can actively participate in the
> standardization process.

Hence, "So What?".

What I really want to know is:  Is the current (beta) spec is now blessed
by the people from "The Document Company bringing you a free and better
ORB than CORBA that doesn't have just C++ in its mind"?

That's more important for me than whether the OMG puts its stamp on it or
not.

--
Fernando D. Mato Mira
Real-Time SW Eng & Networking
Advanced Systems Engineering Division
CSEM
Jaquet-Droz 1                   email: matomira AT acm DOT org
CH-2007 Neuchatel                 tel:       +41 (32) 720-5157
Switzerland                       FAX:       +41 (32) 720-5720

www.csem.ch      www.vrai.com     ligwww.epfl.ch/matomira.html
From: Joachim Achtzehnter
Subject: Re: OMG approves IDL mapping to Common Lisp
Date: 
Message-ID: <x5ln4rl4jl.fsf@soft.mercury.bc.ca>
"Fernando D. Mato Mira" <········@iname.com> writes:
> 
> Is the current (beta) spec is now blessed by the people from "The
> Document Company bringing you a free and better ORB than CORBA that
> doesn't have just C++ in its mind"?

Last official word on this topic was along the lines of Lisp not being
a priority for Xerox/PARC. Unless somebody volunteers to do the work,
the Lisp mapping in ILU will likely not be changed any time soon to
comply with the Franz/OMG mapping. There is also some resistance
because of certain controversial design decisions that were made by
Franz.

For current ILU users with a large body of existing code there is the
additional problem that pretty much every single part of IDL is mapped
differently in the two mappings. This dampens the motivation of
existing ILU users to push for a change to the Franz mapping.

Joachim

-- 
·······@kraut.bc.ca      (http://www.kraut.bc.ca)
·······@mercury.bc.ca    (http://www.mercury.bc.ca)