Members of the forum - In moving over to J7, I had some initial success running existing code by duplicating much of my J6 environment in J7, including copying over all the J6 addons. However, this just highlights how messy my environment has become because of excessive customization.
So, I've resolved to attempt a dual-track approach of working with J7 in parallel with J6, perhaps starting a new project in the new environment and bringing over existing code only piece-by-piece. The first snag I've hit in revamping an existing module is with how I include other code: currently, I use short aliases - defined in PUBLIC_j_ in J6 or Public_j_ in J7 - in my "include" or "require" preambles. My current dilemma stems from a failure to load what I call "dt" for my own date and time code. To fix it, I see that I have the following choices: 1) Define "dt" in Public_j_ to point to the J6 location. 2) Define "dt" in Public_j_ to point to a J7 location and move the file(s) there (bifurcating the code). 3) Extract the items from "dt" that are used in this instance and start a new version of "dt" in J7. 4) Extract the items used from "dt" and re-write them to use more of the standard code provided (giving me a new, different "dt" in J7). 5) Investigate how existing J code management could help with this problem. Does anyone have any suggestions about how to handle this? My ultimate goal is to adopt a migration plan that will give me more modular, transportable code in the future. A major problem with my current, excessive customization is that it's hard to hand off useful modules, e.g. to co-workers, without requiring them to duplicate my entire, idiosyncratic set-up, including parts of my directory structure. I'd like to be able to have them simply install J, then my module - a two-step procedure - instead of the current, multi-step hodge-podge I have now. Any suggestions or hints would be welcome, particularly experience with code management tools. Thanks, Devon -- Devon McCormick, CFA ^me^ at acm. org is my preferred e-mail ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
