Home/ Questions/Q 3985916
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T05:56:55+00:00

I’ve written a module to work with IBMs ClearCase through Powershell. At first it

  • 0

I’ve written a module to work with IBMs ClearCase through Powershell. At first it just contained a couple of often used functions, but now I’m expanding it. Most of the commands have to use a ClearTool object ($ct = new-object ClearCase.ClearTool), but I’d rather not have to recreate that object in every function call as it’s a bit of overhead.

I also create a ClearCase view in many of these functions, but I can simply check for existence of the view and decide not to recreate it.

My question is, what’s the best pattern for this? I can have a “create ct object” function and put the onus on the calling code to maintain it, but I don’t think I like that method. Is it possible to have a module-wide variable for the ClearTool object and have Powershell check to see if it’s filled before trying to recreate it each time?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In the end I created a couple of module-wide variables. I could hide them if necessary, although I haven’t explicitly done that yet. I have a single function to create a view which must be called before doing any actual work and included in that is code to create the ClearTool object. I also have code to set the module-wide variables with the correct ClearTool object for use in other functions and the name of the view.

    In the code of each of the functions if the ClearTool object ($ct) has not yet been set, they return an error condition.

    • 0