Scope of variables when using call

Hi AlexS,

> Thinking about it yeah I could actually just set switchs and process it at the end.

Inline code (even redundant code is far more effective within TCL), so yeah try to avoid [proc] as much as you can.

> eval macros - do you have a link to these and how they work, sound interesting

Below is an example of [eval] macros. 

when RULE_INIT {
	
	set static::my_code_to_execute {
		
			# Define your code which needs to be executed in many places...
		append my_x ""
		append my_x "W"
		append my_x "o"
		append my_x "r"
		append my_x "l"
		append my_x "d"
	}
}
when HTTP_REQUEST {
	
	set my_x "Hello"
	
	# Insert the code above into your code and execute it...
	
	eval $static::my_code_to_execute
	
	log local0.debug $my_x
	
}

Warning: Always define your macro code during RULE_INIT in a static::* variable (use unique names for unique macros). And execute the defined code as shown above. Avoid other [eval] usecases unless you understand the nasty side effects and security implications of [eval]. 

Note:  The RULE_INIT event may be stored in iRule 1 and the HTTP_REQUEST event can be stored in iRule 2. You only need to attach the iRule containing the HTTP_REQUEST event to your Virtual Server. You can basically define global accesible code macros with the outlined technique...

Cheers, Kai