From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3498dd887729ed19 X-Google-Attributes: gid103376,public From: Laurent Pautet Subject: Re: Garbage Collection in Ada Date: 1996/10/21 Message-ID: #1/1 X-Deja-AN: 191012123 sender: pautet@quasimodo.enst.fr references: <01bbb910$f1e73f60$829d6482@joy.ericsson.se> content-type: text/plain; charset=iso-8859-1 organization: Ecole Nationale Superieure des Telecommunications, Paris France mime-version: 1.0 newsgroups: comp.lang.ada Date: 1996-10-21T00:00:00+00:00 List-Id: >>>>> "Jon" == Jon S Anthony writes: Jon> payback". I am clearly not wrong in claiming Orbix/Ada offers Jon> functionally everything (and more) than the Distributed System Annex. Yes ? Is it obvious in a client code to handle an exception (print the exception message) that has not been declared in a server spec ? Is it obvious to ensure remote asynchronous transfert control in CORBA ? How do you implement share data (matrix and slices) ? And atomic operations on these data ? These are of course examples but it is very easy to find features that are impossible or complex to write with CORBA (even remote object features) and that are very easy with Annex E. Of course, you will be able to implement complex features with CORBA, but you're going to write everything with some kind of message passing (or asynchronous RPCs) when DSA would provide exactly what you are looking for. Of course, it could be very interesting to implement DSA on the top of CORBA because in some respects, " offers functionally everything (and more) than " :-)