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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,8f01d35116e753b6 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.232.169 with SMTP id tp9mr26266828pbc.6.1332938952636; Wed, 28 Mar 2012 05:49:12 -0700 (PDT) Path: z9ni11294pbe.0!nntp.google.com!news1.google.com!volia.net!news2.volia.net!feed-A.news.volia.net!news.musoftware.de!wum.musoftware.de!newsfeed.straub-nv.de!noris.net!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 28 Mar 2012 14:48:41 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: xor References: <9t8mq9Fla4U1@mid.individual.net> <9t99r9F6e2U1@mid.individual.net> <4f72393e$0$6643$9b4e6d93@newsspool2.arcor-online.net> In-Reply-To: Message-ID: <4f7308a9$0$7625$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 28 Mar 2012 14:48:41 CEST NNTP-Posting-Host: 7ad3f7e9.newsspool1.arcor-online.net X-Trace: DXC=ogX`YO=V?[C^B]`=U:WelBic==]BZ:afN4Fo<]lROoRA<`=YMgDjhgB@:>SDEfdW7Fnc\616M64>JLh>_cHTX3jM7LJ_`mX\oKL X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Date: 2012-03-28T14:48:41+02:00 List-Id: On 28.03.12 14:18, Michael Moeller wrote: > While this example compiles without complaints it > doesn't work with procedures declared in my package. How can I > make Sequential_IO visible there? Instantiate Sequential_IO where you need it: If the instance is needed in several packages, one solution is to create the instance at library level (for GNAT, read: in a file that only declares UB_IO). Then, add a with clause for this instance (UB_IO) everywhere you need visibility of UB_IO. (This is what context clauses are about; the other part of visibility is nesting.) -->8-- with Package_Defining_UByte; package UB_IO is new Sequential_IO (Package_Defining_UByte.Ubyte); --8<-- with UB_IO; package One is ... with UB_IO; package Two is ... > Its a little strange, though, how dead easy coding concurrency > on a Sun machine was recently while I'm not able to write out > some silly bytes using the very same language. This is not unusual, I think, insofar as virtually every language requires some effort when I/O is more than "print". Python, Java, Ada, C, C++, they all have some frowned upon simple I/O procedures, and then the real thing. The latter takes time getting used to. (A really good .NET programmer (C#) told me that, now that he needed to rewrite some software in Java (after a company takeover), he noticed that he didn't know the first things about formatting numbers in Java... Of course, he knew about formatting in general which made learning easier for him.)