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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,41c5dc8789baf2f3 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Received: by 10.181.11.234 with SMTP id el10mr81595wid.2.1347976023412; Tue, 18 Sep 2012 06:47:03 -0700 (PDT) Received: by 10.236.192.168 with SMTP id i28mr44057yhn.7.1347976023253; Tue, 18 Sep 2012 06:47:03 -0700 (PDT) Path: ed8ni114471314wib.0!nntp.google.com!v8no62729qap.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 18 Sep 2012 06:47:03 -0700 (PDT) In-Reply-To: <5058167c$0$285$14726298@news.sunsite.dk> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=195.58.145.51; posting-account=28F2IwkAAACL1Z5nRC-dE7zuvWdbWC7P NNTP-Posting-Host: 195.58.145.51 References: <5058167c$0$285$14726298@news.sunsite.dk> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <0b087f0c-bc16-4e10-aa8b-0b7281e4b62c@googlegroups.com> Subject: Re: Understanding Visibility From: tonyg Injection-Date: Tue, 18 Sep 2012 13:47:03 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-09-18T06:47:03-07:00 List-Id: On Tuesday, 18 September 2012 07:36:45 UTC+1, Thomas L=F8cke wrote: > On 09/17/2012 10:42 PM, tonyg wrote: >=20 > > >=20 > > I needed to log some stuff from several tasks in one program. So I wrot= e a little logging package. I used a package containing several text_io.fil= e_types followed by a protected object to make sure the file operations wer= e not interfered with. >=20 > > However when things were passed through to inside the protected ob= ject I found that the file was not taking the information being passed to i= t. Can anyone explain this to me, as I think the file should be visible. >=20 > > >=20 >=20 >=20 >=20 >=20 > You could take a peek at how they solved the problem in the GNATCOLL >=20 > package, specifically the Traces part: >=20 >=20 >=20 > http://docs.adacore.com/gnatcoll-docs/traces.html >=20 >=20 >=20 > It works flawlessly, or rather I've not been able to trash it yet. :D >=20 >=20 >=20 > Another option is Alog from codelabs: http://www.codelabs.ch/alog/ >=20 >=20 >=20 > And a third one is grabbing AWS and look at their AWS.Log package. >=20 >=20 >=20 > Lots of good stuff to learn from. >=20 >=20 >=20 > Personally I use GNATCOLL.Traces for most of my logging needs, as it >=20 > can log to syslogd, which I find very handy. >=20 >=20 >=20 > --=20 >=20 > Thomas L=F8cke | thomas@12boo.net | http://12boo.net I noticed that alog has debian wheezy packages supported \o/ so I am taking= a good long look at that rather than gnatcoll which needs to be installed = from source. Its looking good so far.