Replace code throughout OSpace

I am quite new to Livelink, its Builder respectively.One of my first tasks is to refactor legacy code, in the course of which I want to rename variables throughout the entire OSpace of a decent number of modules.Now my question: is it save to make a dump of OSpace and do my replacements in this single file and after that to re-import the dump file?

Find more posts tagged with

Comments

Greg_Griffiths_(ggriffiths_-_(deleted))

Juergen, It is usually recommended to make the changes via Builder so that you can compile and test as you go through, otherwise if you have an issue you may spend a lot of time refactoring the code.

(inactive)_Jürgen_Riemer

Greg,thanks for your reply. I see you point, yet if I have to i.e. change the name of a SQL table in in all my scripts I would think it is more error prone to do this in the builder script by script.Question is, are there any implications I have to consider when falling back on the dump file/re-import method?

(inactive)_Jürgen_Riemer

It would be nice if one of the developers could chip in their thoughts in this concern. How would you proceed if you had to change variable names throughout the entire OSpace (more than 100 locations) .. would you really do that going into every script using the builder interface?thanks for any additional inputJuergen