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,5882b8e137d950f8
X-Google-Attributes: gid103376,public
From: Robert A Duff <bobduff@world.std.com>
Subject: Re: DII COE bars Ada -> Java compilation
Date: 2000/04/05
Message-ID: <wcc3dp0vgki.fsf@world.std.com>#1/1
X-Deja-AN: 607050558
Sender: bobduff@world.std.com (Robert A Duff)
References: <38EB3482.971747E4@lmco.com>
Organization: The World Public Access UNIX, Brookline, MA
Newsgroups: comp.lang.ada
Date: 2000-04-05T00:00:00+00:00
List-Id: <comp.lang.ada>

"Marc A. Criley" <marc.a.criley@lmco.com> writes:

> To Ada to JBC compiler vendors:
> 
> Section 8.2.3 (Miscellaneous) of the Defense Information Infrastructure
> Common Operating Environment (DII COE) Integration & Run-Time
> Specification (I&RTS) v4.0 states that "Developers shall not use
> compilers designed to convert code developed in other languages (e.g.,
> Ada, C++) to create Java byte-codes. This restriction is important
> because such compilers may inadvertently bypass intended Java security
> features."
> 
> Is this a legitimate concern?

No.

- Bob