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,c0f035b936128b6c X-Google-Attributes: gid103376,public X-Google-Thread: 1014db,c0f035b936128b6c X-Google-Attributes: gid1014db,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Ada95 to ANSI_C converter Date: 1997/03/31 Message-ID: #1/1 X-Deja-AN: 229818639 References: <5hbrah$ctt$1@gail.ripco.com> <01bc3a3d$7734db20$63f482c1@xhv46.dial.pipex.com> <5heoel$bc0$1@gail.ripco.com> Organization: New York University Newsgroups: comp.lang.ada,comp.lang.c Date: 1997-03-31T00:00:00+00:00 List-Id: Jon says (of translating Ada to C) <> OK, tell me how you intend, in ANSI C, to handle finalization and exceptions, or integer overflow checking, or .... If you are not confinced of the problem, I would guess you have not looked into it closely. Now of course the inefficiency may be acceptable, but there is no question that there are fundamental inefficiencies in this approach. <> Well I am not sure what you mean by "trash" here, I didn't see any such messages. I did see messages that assumed she was looking for readable C. The reason is that it is relatively hard to imagine a scenario for her questions that does not need readable C, but we can let her speak for herself.