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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, TO_MALFORMED autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,6d51a4400ccde5d8 X-Google-Attributes: gid103376,public From: Samuel Tardieu Subject: Re: Ada/Java Date: 1997/04/23 Message-ID: #1/1 X-Deja-AN: 236802994 Sender: tardieu@esmeralda.enst.fr References: <5j2r5d$s1p@lotho.delphi.com> <5jh808$g9n@news.ida.org> <335CDAF1.178A@bix.com> Mail-Copies-To: sam@ada.eu.org To: jsa@alexandria (Jon S Anthony) Organization: TELECOM Paris Newsgroups: comp.lang.ada Date: 1997-04-23T00:00:00+00:00 List-Id: >>>>> "Jon" == Jon S Anthony writes: Jon> In article <335CDAF1.178A@bix.com> Tom Moran Jon> writes: >> Must each record be a class? Not all Ada records are tagged types. Jon> Java does not support any other kind of first class object which Jon> has structure. So, yeah, this (currently) must be... Well, not exactly. You can always choose to group several Ada records into one Java class if your goal is to minimize the number of class files, and then use one part of the class or the other. You can even use overlapping if you have fields of the same type in several records. Note that this approach works well only with non-tagged records since these Java classes will be deriving from java.lang.Object, it would be more difficult with tagged records since you don't want to loose the virtual dispatching capabilities. Sam -- Samuel Tardieu -- sam@ada.eu.org