Hi,

Does anyone know if there is a way to declare that all globals created in a subprotocol should be scoped as Local and not global?

I know you can declare named ones, but this opens up a risk that new ones could be missed.

Is there some secret wildcard we can use in the DeclareLocal parameter box?  I'm hoping there might be an "Easter Egg" feature not documented in the help. I tried * but it didn't work 😞 

If there is no way to do this, is there any easy way to get a list of all globals in a subprotocol, so at least we could be confident all have been DeclaredLocal?

The Display Globals,  PreTest Global Leakage and PostTest Global Leakage components  only display globals after they have been "executed", which means all possible pipes / components / pilotscript combination would need to be executed to see them (which can be hard to ensure). 

The ctrl-F with an @, only searches the top level subprotocol and not any shortcuts it calls (unless they are opened manually in the pro client) and is very manual and error prone.

The only way I can think of doing this is with some regex looking for @s and reading in the subprotocol and any shortcut protocol(s)  .xmls files to get a list of probable globals.

I know best practice is to DeclareLocal for good reasons, but I'm hoping to find a better, easier way to ensure this is used.

Thanks in advance

Joe