This was not my statement, it was one I was quoting. However, to clarify how I did stumble here, I started with a function that had lines like these two: ccix=. 0 NB. Initialize Customer Cluster index ... ccix=. >:ccix NB. Increment cc index ...
Subsequently, the incrementing line was moved into a sub-function and turned into a global assignment ccix=: >:ccix with the idea I didn't want to bother with repeating ccix at the end of the new function and calling the new function like this: ccix=: newFunction args;ccix Later, I changed my mind and did it this latter way; however, I neglected to modify my initialization to a local variable, hence the error. On 1/2/07, dly <[EMAIL PROTECTED]> wrote:
The whole concept of local and global variables is to deal with assigning the same name both locally and globally. If your statement is meant to have some meaning, could you please rephrase it? dly [EMAIL PROTECTED] On 3-Jan-07, at 12:48 AM, Devon McCormick wrote: >> I expect that it was that assigning the >> same name both locally and globally was more often a frustrating >> mistake >> than a useful intentional decision. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
-- Devon McCormick ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
