VANCE,JEFF (HP-Cupertino,ex1) wrote:
> Jim writes:
>
>>I really think it is too restrictive not to be able to qualify
>>a function name.  It is certainly unlike command files.
>>
>>I suggest that there be some kind of escaping mechanism for
>>the function name:
>>
>>  f()
>>  "f.b.a"()
>>  "/A/B/F"()
>>
>>Quotes might not be the best escape character.  I'm not sure.
>
>
> It would be real tough to get quotes to be an escape character
> since they enclose string values also. The parenthesis and lack
> on intervening operator would need to be the clues but the evaluator's
> parser does not support this much lookahead. Maybe square brackets, but
> they also allow quotes inside...

I personally can live with the HPPATH solution for unqualified user function
names that I might use in my own code.

But what about curly brackets ("{}")?  AFAIK these do not yet have any meaning
to the CI.  I admit though that things like {f.b.a}() would look rather ugly.
--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *