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: 1014db,c0f035b936128b6c
X-Google-Attributes: gid1014db,public
X-Google-Thread: 103376,c0f035b936128b6c
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Ada95 to ANSI_C converter
Date: 1997/03/26
Message-ID: <dewar.859432540@merv>#1/1
X-Deja-AN: 228681233
References: <5hbrah$ctt$1@gail.ripco.com>
 <01bc3a3d$7734db20$63f482c1@xhv46.dial.pipex.com>
Organization: New York University
Newsgroups: comp.lang.ada,comp.lang.c
Date: 1997-03-26T00:00:00+00:00
List-Id: <comp.lang.ada>


Nick says

<<Essentially, this is a task which should be quite feasible, as long as a
moderately pragmatic approach is taken (IMHO!).>>

Only if you restrict the Ada 95 to a very small subset. There are many
features in Ada 95 that will cause significant trouble in converting to
C (e.g. nested procedures, dynamic aggregates, dynamic arrays, particularly
those in records, variant records, finalization, exceptions, packed arrays,
etc. etc.)