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.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,7f4d16c4ee371eb5 X-Google-Attributes: gid103376,public From: kilgallen@eisner.decus.org (Larry Kilgallen) Subject: Re: Why is it Called a Package? Date: 2000/03/27 Message-ID: <2000Mar27.111655.1@eisner>#1/1 X-Deja-AN: 603003293 References: <38DF7F38.8D656ABD@lmtas.lmco.com> X-Trace: news.decus.org 954173819 19432 KILGALLEN [216.44.122.34] Organization: LJK Software Reply-To: Kilgallen@eisner.decus.org.nospam Newsgroups: comp.lang.ada Date: 2000-03-27T00:00:00+00:00 List-Id: In article <38DF7F38.8D656ABD@lmtas.lmco.com>, Gary Scott writes: > Admittedly a "fluff" question... > > I notice that a lot of modern languages choose names/syntax that I > personally do not find intuitive. Other languages contain basically the > same feature but call it by different names (module, etc.). Why was > "package" considered the intuitive name for this feature? I was not there when the decision was made, but I would presume the goal was to _avoid_ using a familiar name since other languages do not typically have something that behaves in this fashion. If one were to propose the term "module", for instance, those who knew other programming languages and were learning Ada might presume that it worked like a "module" in those other languages, and they would be wrong. I program in several languages that have "modules" and those "modules" do not support separately compiled specifications and bodies, cannot be nested within other "modules", etc.