Forum OpenACS Q&A: Re: Problems defining procs

Collapse
13: Re: Problems defining procs (response to 12)
Posted by ultra newb on 06/11/11 01:07 AM
I stated several times that I put this proc definition in a "blah-procs" file in a tcl folder. In other words, I put it in a file that is supposed to "auto-run" when the system starts.
Collapse
25: Re: Problems defining procs (response to 13)
Posted by Andrew Piskorski on 06/12/11 07:18 PM
I stated several times that I put this proc definition in a "blah-procs" file in a tcl folder.

Which is not a way to "dynamically define this proc".

Collapse
26: Re: Problems defining procs (response to 25)
Posted by ultra newb on 06/13/11 01:39 AM
What's the correct way to do it? (current way seems to be working now)
Collapse
27: Re: Problems defining procs (response to 26)
Posted by Jim Lynch on 06/13/11 11:11 AM
so the proc has to return a list... that's not a problem, a list is a string. I'm really, really skeptical when you say the proc has to be dynamic; there's a database you can use, are the values you need to return in the database?
Collapse
28: Re: Problems defining procs (response to 27)
Posted by ultra newb on 06/13/11 03:41 PM
No, the values are in a backend system I wrote in another programming language (a server). These values change from time to time. I'd like to avoid having to change values in the openacs system (front end) when the values on the backend change. I thought the best and cleanest approach was to make a dynamic proc (the memoized approach one person recommended works also).

At any rate, everything is working fine now. The problem (as someone pointed out) was accessing a system proc when there wasn't a connection.