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,99ab4bb580fc34cd X-Google-Attributes: gid103376,public From: dewar@cs.nyu.edu (Robert Dewar) Subject: Re: Q: access to subprogram Date: 1996/07/03 Message-ID: #1/1 X-Deja-AN: 164035197 references: <4rd5lu$q4@mulga.cs.mu.OZ.AU> <4re8bj$qfk@krusty.irvine.com> organization: Courant Institute of Mathematical Sciences newsgroups: comp.lang.ada Date: 1996-07-03T00:00:00+00:00 List-Id: Adam said "It should be noted that the new object-oriented features of Ada 95 should make subprogram accesses less necessary than before. Abstract types inherently possess subprogram pointers, so it should be possible to take advantage of this feature as an alternative to explicit subprogram accesses." One nice demonstration of this is to look at the approach taken by Intermetrics in their Ada 95 compiler that generates JBC. Java does not have subprogram pointers, but their Ada 95 compiler can exactly model Ada 95 subprogram pointers by making them correspond to a class with a method that calls through the "pointer".