It might help to consider each adp page (or include'd page) as a tcl
proc. As such, if you define the variable on the page, it will be
visible there:
<%
set bob 1
%>
<%= $bob %>
<% ns_adp_puts $bob %>
However, things defined in ot
On Saturday 19 April 2008 16:59, Xavier Bourguignon wrote:
>
>
>
>
> <%proc_call%>
> <%ns_adp_puts $varname%>
>
>
>
> Unless varname is global in proc_call, then it seems that varname is
> unknown to the tcl interpreter.
>
Is this a working or non-working example? There are l
<%proc_call%>
<%ns_adp_puts $varname%>
Unless varname is global in proc_call, then it seems that varname is
unknown to the tcl interpreter.
How do you get away with not using adps? They are the building blocks
of dynamic pages aren't they?
Thanks
On 19/04/2008, Tom Jackson
On Saturday 19 April 2008 12:52, Xavier Bourguignon wrote:
> Hi,
>
> In one of my adp files I want to display the value of a tcl variable,
> so I do this <%=$varname%>
>
> My problem is that I can only see the value when my varname is set to
> global in my tcl script?
>
> My question is: Why does t
Hi,
In one of my adp files I want to display the value of a tcl variable,
so I do this <%=$varname%>
My problem is that I can only see the value when my varname is set to
global in my tcl script?
My question is: Why does the variable have to be a global? can't I do
set varname varvalue and then
Everyone,
I've updated nsfreetds in CVS HEAD to work with FreeTDS 0.64. I haven't
tagged a release yet, as I'm looking for feedback from testers to make
sure there aren't any critical problems with the changes.
There are some new configuration parameters to control the database
connection. I've
