The approach I would take is to keep all custom code in a separate file, and make sure that file gets loaded after J initializes the 'standard' files.
you can either maintain a live redefinition like: standardJverb=: Mycode@:(standardJverb f.) NB. if your sure your redef file will only be executed once. The above will update functionality for standardJverb whatever future versions of that verb might be. If you don't want the functionality to ever be "upgraded" (euphemism for broken), you can just copy the definition and edit it with your own, and this also has the advantage of being resilient to multiple execution. ----- Original Message ---- From: bill lam <[EMAIL PROTECTED]> To: Programming forum <[email protected]> Sent: Tuesday, November 7, 2006 9:10:01 AM Subject: Re: [Jprogramming] updating core library question Chris Burke wrote: > If the change is specific to your use of the system, then it should be > saved elsewhere, perhaps in your startup script. The modifications are usually unicode related, eg unicode safe version of tolower, toupper and wdinfo. I guess users within the euro countries will also be affected becasue the euro sign is U+20AC, if there a sentence in scripts saytotal=: '€', ":total then case-insensitive search using find dialog will raise an error index error: tolower txt=. tolower FIWTEXT But there are only few minor modifications, I'll look further if using diff3 in batch mode can get the done job at least semi-automatically. -- regards, bill ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
