On Oct 6, 2009, at 4:35 AM, Robert Purves wrote:

>
> Robert Covington wrote:
>
>> I don't see how they can overly complicate the editor or FBtoC  
>> that much, seeing how they have worked ok for years, and even with  
>> FBtoC. Def might should be for Def fns in code, not helper  
>> functions, but Usr was not that abstract at all.
>
> usr() started life as a way of calling a 6502 machine-language  
> routine on the Apple ][, and I was a big fan of it then. But now it  
> is an anomaly.

Did not know that. Thunk it a contraction for a way to notify the  
users of FB that it was a User- helpful routine (i.e. Usr  
FSFileExists, which is a far cry from any assembly anything)

>
>> If you are going to remove them,   then perhaps instead of a black  
>> and white approach of making them all generic,  to avoid collision  
>> with existing code and to make it easy to know you are calling a  
>> handy runtime function, maintaining some manner of intuitiveness,   
>> at least consider to rename any changed items to Fn  
>> UsrSomeHandyRuntimeSomethingOrOther, with a Usr prefix.
>
> The familiar names (ApplescriptRun, CheckOneItem,  
> SetButtonFontStyle, ReplaceResource...) will continue to highlight  
> as keywords even when prefaced by 'fn'; I hope that this allays  
> your concern for 'intuitiveness'.
>
> Robert P.

Was seeking something to delineate the soon to be less visibly  
categorized Usr (as in User helping) denizens from the usual  
toolboxes, keywords, etc. so one knows what is what.

So as to avoid having things like my and others Fn FsFileExists from  
colliding with the new USR item which will now be the same name, I  
reckon, along with anything else that now becomes generic.

Robert