Forum OpenACS Q&A: Re: Problems defining procs

Posted by ultra newb on
Yes, I know the "normal" way. I don't want the normal way in this instance because I need the definition of the proc to change based on certain circumstances.

What I need is a proc that returns a list of values. The list of values changes day to day. I want the list of values to come from a backend database. I want the proc to be defined dynamically at startup to return that list of values. I don't want to have to connect to the backend database each time I need the list of values - I just want to connect one time at system startup, get the list of values, and have that list of values "hard-coded" in the proc.

This is easy to do. In fact, I've tested it outside of OpenACS and it works just fine (TCL is made to do stuff like this). It just doesn't work in OpenACS for some reason.

Is there some reason why this sort of definition is not possible in OpenACS or AOLServer?

Posted by Claudio Pasolini on
Here is a small example of how to dynamically define a proc:

# get/set the values
set day_values "aaa bbb ccc"
set myproc "
proc myproc {} {
puts \"The day's values are: $day_values\"
eval $myproc

The values get hardcoded into the proc.

Posted by Jeff Rogers on
The util_memoize procs are for exactly this purpose - run something once and return it quickly after that.

You can wrap it in a proc very easily too, for example:

proc get_values {} {
return [util_memoize get_values_internal 86400]

proc get_values_internal {} {
# do slow/heavy database access
return $values