nested functions

Kenneth Brody kenbrody at spamcop.net
Wed Feb 25 17:01:47 PST 2015


On 2/25/2015 5:43 PM, Richard Kreiss wrote:
>
>
>> -----Original Message-----
>> From: Filepro-list [mailto:filepro-list-
>> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Kenneth
> Brody
[...]
>> On 2/25/2015 11:53 AM, Richard Kreiss wrote:
[...]
>>> However, this proved to create a problem as there was a space between
>>> the first and last name.  Only the first name was being passed by -ry.
>>> My fault.  I then added a comma to the name value and created
>>> programming to remove the comma.
>>
>> Put the parameter in quotes:
>>
>>       -ry "Bob   Smith"
>
> Ken, I was avoiding of "playing" with quotes inside of quotes.  Although
> this is probably a better solution.

You can always do something like

     In @ONCE, put

         declare quote(1,*,g) ; quote = chr("34")

     Then, the SYSTEM command would be:

         system "whatever ... -ry " & quote & last & first & quote & " ..."

>>> My question is how complex can one use before filePro has a problem
>>> handling it. (assuming that the functions are used properly)
>>
>> What do you mean by "how complex can one use"?
>
> Your response below answers the question, keep the programming line simple
> unless is going to be executed a great number of times.

And, even if it is executed "a great number of times", unless the complex 
version of the processing is faster, "human readable" is still more important.

> In this case,  the line is executed once.

Okay.

[...]

-- 
Kenneth Brody


More information about the Filepro-list mailing list