"Adam Beneschan" <adam@irvine.com> wrote in message 
news:adc832ae-94f1-43eb-b119-be9767888a19@googlegroups.com...
...
>> I'm not certain what the convention of this procedure is (it might be
>> defined to be "intrinsic" somewhere, in which case you couldn't take 
>> 'Access
>> to it, I can't find such a rule on a quick check of the RM).
>
>6.3.1(4): The Intrinsic calling convention represents subprograms that are 
>�built in�
>to the compiler. The default calling convention is Intrinsic for the 
>following: ...
>
>6.3.1(10.1/2) any prefixed view of a subprogram (see 4.1.3).

Thanks. I looked for that, but couldn't find it.

...
>> But it surely
>> exists and should not report that "selector "Print" doesn't exist.
>
>Yep, the error message appears to be wrong, but I can sort of understand 
>it.  If the
>compiler knows that a prefixed view wouldn't be allowed here (as a prefix 
>to 'Access),
>then since it has to do name resolution (in case Print is overloaded), it 
>might be using a
>different search routine than it would use if it were processing a 
>procedure call.  Or
>something like that.

I can "understand" how the message came about, but that's unlikely to help 
the poor programmer who can't figure out the problem. Or even the harried 
language-lawyer who is certain that the prefix is legal... :-)

                                 Randy.