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=-2.9 required=5.0 tests=BAYES_00,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,f297d5b850ee1e61 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-03-06 11:50:17 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeed.berkeley.edu!ucberkeley!freenix!enst.fr!not-for-mail From: sk Newsgroups: comp.lang.ada Subject: Re: Ada2005 clear screen etc. Date: Thu, 06 Mar 2003 13:54:57 -0600 Organization: ENST, France Message-ID: References: <87f5a614.0303011527.4cb09de2@posting.google.com> Reply-To: "comp.lang.ada mail to news gateway" NNTP-Posting-Host: marvin.enst.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: avanie.enst.fr 1046980146 39815 137.194.161.2 (6 Mar 2003 19:49:06 GMT) X-Complaints-To: usenet@enst.fr NNTP-Posting-Date: Thu, 6 Mar 2003 19:49:06 +0000 (UTC) To: "comp.lang.ada mail to news gateway" Return-Path: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020828 X-Accept-Language: en-us, en X-BeenThere: comp.lang.ada@ada.eu.org X-Mailman-Version: 2.1 Precedence: list List-Id: comp.lang.ada mail to news gateway List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Xref: archiver1.google.com comp.lang.ada:34989 Date: 2003-03-06T13:54:57-06:00 Hi, Stephen.A.Leake@nasa.gov : > ... ANSI standard ... I was more panicing over the thought that the language be bound to some possibly transient fashion and hadn't stopped to consider some never dying, ubiquitous things like the ANSI terminal standard. However, I tend towards the comment > Because the Ada standard should be for things that require > support from the compiler vendor. and subsequent comments on the response cycle for a set of libraries. With that thought, how about an official but very flexible and distinctly separate package hierarchy ? (.. and I am sure it has been discussed before or there are comments as part of the Ada200y process, sorry for lack of opportunity to fully investigate. Also please note that I am not familiar with any of the ongoing Ada library projects or the "C++" standard library so, again, sorry if this is a rehash of other discussions or duplication of ideas so RTFM me, with URL, if appropriate). Standard Ada.xxx Interfaces.xxx System.xxx Libraries.xxx "Libraries" just a graft point, nothing significant about the name. "Libraries" would, by agreement, have some invarient subtrees. Perhaps two levels of abstract/conceptual packages before specific solutions are grafted into the tree ? Libraries.Vendor (invarient, children as needed) .Gnat. .Os_Lib; ... .RRSoftware .Claw ... Libraries.Host (invariant, children as needed) .Linux .Windows .Win32Ada Libraries.Host_Interfaces. .Console. .ANSI_Terminal .VT100_Terminal ... .Graphical .Win32Ada renames Libraries.Host.Windows.Win32Ada .GtkAda ... .File_System ... .Network .Transport .Sockets ... .Protocols .Smtp .Http ... .etc Libraries.Objects_And_Methods .Containers . .Strings Libraries.Standardized_Interfaces .Posix .RFCs etc There are a lot of crossovers, but Ada has the "renames" mechanism which could associate "Libraries.Vendor.Gnat.Directory_Operations" for example, with "Libraries.Host_Interfaces.File_System.Directories" This needs a lot more thought and work (rearrangment, better nameing, interdependencies, circularity, management burden etc), however, it could provide a more cohesive framework into which APIs would fit without burdening the core language or its "Ada.*" package hierarchy. -- ------------------------------------------------- -- Merge vertically for real address -- -- s n p @ t . o -- k i e k c c m -------------------------------------------------