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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c6546cb6e04b1761
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: __FILE__ and __LINE__
Date: 1997/04/08
Message-ID: <dewar.860508578@merv>#1/1
X-Deja-AN: 231553705
References: <5ia77f$go3@nlrgup.nlr.nl> <dewar.860416526@merv>
 <5id07f$3ap@nlrgup.nlr.nl>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-04-08T00:00:00+00:00
List-Id: <comp.lang.ada>


i<<    You're right. Attributes are preferred (also from a user's point of
view). I've thought about Attributes for this job, but I couldn't find
appropriate Attributes. Furhermore, I couldn't figure out where they
should be Attributes of.
>>

Actually, thinking about this more, I prefer a standard package to the
use of attributes:

  package Compile_Time_Info is
     function Time_Compiled return Calendar.Time;
     function Line_Number return Natural;
     function Source_File_Name return String;

     pragma Import (Intrinsic, Time_Compiled);
     pragma Import (Intrinsic, Line_Number);
     pragma Import (Intrinsic, Source_File_Name);

     etc ..
  end Compile_Time_Info;

This of course requrires compiler assistance (any solution to this problem
does), but this seems the cleanest approach. It would not be hard to 
implement in GNAT, but there are no plans to do so currently