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=0.6 required=5.0 tests=BAYES_05,INVALID_DATE, MSGID_SHORT autolearn=no autolearn_force=no version=3.4.4 Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!mailrus!tut.cis.ohio-state.edu!ut-sally!utah-cs!utah-gr!uplherc!sp7040!obie!wsccs!wes From: wes@wsccs.UUCP (Barnacle Wes) Newsgroups: comp.lang.ada Subject: Re: Protection for Ada Binary Libraries Message-ID: <250@wsccs.UUCP> Date: 3 Mar 88 20:59:29 GMT References: <324@ajpo.sei.cmu.edu> <57900063@ada-uts> Summary: Protecting library sources - DEC *really* has this down pat! List-Id: In article <57900063@ada-uts>, offer@ada-uts writes: > 1. Most compilers, and in particular, those that use DIANA, have a > mechanism to not include the source (or some form of internal > representation of the source) in the program library, the reasons > being: reducing the size of those libraries and keeping bodies' source > code proprietary (e.g. the implementation of TEXT_IO). The disadvantage > is clearly the inability the see the source at debug time and also > the inability to provide pretty-printing/interspersed source/assembly > listings. DEC really has this down pat in the VAX/Ada compiler. They have the source for the Ada interfaces to the Ada RTL available any time you are in ACS. The source for the libraries themselves are an entirely different manner. The libraries aren't even written in Ada; the Ada bindings are IMPORT PRAGMAS to link to the Bliss calling sequences. The libraries (I would assume) are written in Bliss-32. Remember: "Bliss is ignorance!" (Terry Lambert). -- /\ - " Against Stupidity, - {backbones}! /\/\ . /\ - The Gods Themselves - utah-cs!utah-gr! / \/ \/\/ \ - Contend in Vain." - uplherc!sp7040! / U i n T e c h \ - Schiller - obie!wes