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.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.50.13.69 with SMTP id f5mr144991igc.7.1456426236675;
        Thu, 25 Feb 2016 10:50:36 -0800 (PST)
X-Received: by 10.182.112.202 with SMTP id is10mr561039obb.7.1456426236642;
 Thu, 25 Feb 2016 10:50:36 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!hb3no9000565igb.0!news-out.google.com!k1ni912igd.0!nntp.google.com!hb3no9000558igb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Thu, 25 Feb 2016 10:50:36 -0800 (PST)
In-Reply-To: <c67795ee-f64f-4591-af52-ea3e062d7f28@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2001:470:9174:2:5cdf:2add:e9f5:239e;
 posting-account=r0RePAgAAABkc8iAou09Mtfbf-fnKQql
NNTP-Posting-Host: 2001:470:9174:2:5cdf:2add:e9f5:239e
References: <3acc13a4-d92e-498b-8dbe-cb2e399c54ed@googlegroups.com>
 <1456246988.16316.22.camel@obry.net> <dj43mmFo9gtU1@mid.individual.net>
 <09392c3a-b79b-49d3-ab7c-0f90d0f454eb@googlegroups.com>
 <ly1t81m8vp.fsf@pushface.org>
 <c67795ee-f64f-4591-af52-ea3e062d7f28@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3cbd30e8-899e-45d4-9aa9-72e45b81f96c@googlegroups.com>
Subject: Re: Outrageous Thoughts on Ada Compilers.
From: MM <mrvmurray@gmail.com>
Injection-Date: Thu, 25 Feb 2016 18:50:36 +0000
Content-Type: text/plain; charset=ISO-8859-1
Xref: news.eternal-september.org comp.lang.ada:29611
Date: 2016-02-25T10:50:36-08:00
List-Id: <comp.lang.ada>

On Thursday, 25 February 2016 16:37:19 UTC, Austin Obyrne  wrote:
> Every compiler uses ASCII as its eventual output domain i.e. the eventual compiler
> source code is some combination of the 95 elements of ASCII.

This is unbelievably confused.

1) The "source code" is *input* not output.
2) The output of a compiler is executable instructions.

> *I can encrypt these to form a customised version of the parent compiler.

Encrypted code is NOT customised code. Encrypted code will neither compile nor
execute unless you somehow build a seriously specialised tool to do this. I suggest
you learn how to do ROT-13 first.

> I can then manage this with another entity to create a unique loop for our sole use.

OK. Demonstrate this. I bet you can't.

> There is no need to go back to machine code??

How will your programs run, then?

> <Do you know how to access the compiler sourcecode?
> <For GNAT, yes; otherwise, no.
> 
> That alone may be sufficient to disable the compil;er in question.??

Hardly.

Simon knows where the compiler source that he is interested in is. Him not knowing
this disables nothing; somebody else will know.

M
--