Re: expression function bug or think?

[Niklas Holsti <niklas.holsti@tidorum.invalid>]

Martin wrote:
> On Jun 17, 11:33 am, Simon Wright <si...@pushface.org> wrote:
>> Martin <martin.do...@btopenworld.com> writes:
>>> On Jun 16, 9:41 pm, Simon Wright <si...@pushface.org> wrote:
>>> [snip]
>>>> package functions is
>>>>    function functions__fib (n : natural) return natural;
>>> Thanks for this - this confirms something I'd been told wasn't the
>>> case - when compiling GNAT, non-standard identifiers _are_ created and
>>> allowed (in this case a name with a double underscore)!
>> I think this only happens when GNAT recreates the processed source to
>> show you what it did.
> 
> Ahhh! Thanks...wonder what the internal reference looks like...or is
> there one at all and it just creates these names when this option is
> selected? If I had a 28 hour day, I might find out!

I'm not sure what your question really is, but if it is about the way 
GNAT generates link names for Ada entities, this is explained in the 
GNAT User's Guide. Quote (from the version for GCC 4.3.0):

"25.2 The External Symbol Naming Scheme of GNAT

In order to interpret the output from GNAT, when using tools that are 
originally intended for use with other languages, it is useful to 
understand the conventions used to generate link names from the Ada 
entity names. All link names are in all lowercase letters. With the 
exception of library procedure names, the mechanism used is simply to 
use the full expanded Ada name with dots replaced by double underscores. 
For example, suppose we have the following package spec:

package QRS is
    MN : Integer;
end QRS;

The variable MN has a full expanded Ada name of QRS.MN, so the 
corresponding link name is qrs__mn."

The name "functions__fib" in the recreated source, above, follows this rule.

-- 
Niklas Holsti
Tidorum Ltd
niklas holsti tidorum fi
       .      @       .