Am 01.06.2005 um 22:50 schrieb Stephen Deasey:
Because form input always needs to be checked. You can't declare it
debugged and turn off exception checking. People will continue to
feed your program broken/malicious input.
Ah, this is what you mean! What about fixing tcllib to allow two
ty
On 6/1/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 01.06.2005 um 22:23 schrieb Stephen Deasey:
>
> > That's a useful feature, but not when you're checking
> > form input!
>
> Why not?
Because form input always needs to be checked. You can't declare it
debugged and turn off excepti
Am 01.06.2005 um 22:23 schrieb Stephen Deasey:
That's a useful feature, but not when you're checking
form input!
Why not?
On 6/1/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 01.06.2005 um 21:30 schrieb Stephen Deasey:
>
> > For input
> > validation, some other mechanism should be used.
> >
>
> Input of what kind? From Tcl or from C?
> Do you mean form-input? Why you can't apply the
> tcllib assertion on
Am 01.06.2005 um 21:30 schrieb Stephen Deasey:
For input
validation, some other mechanism should be used.
Input of what kind? From Tcl or from C?
Do you mean form-input? Why you can't apply the
tcllib assertion on form-input, if this is what you mean?
Zoran
On 6/1/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 01.06.2005 um 13:24 schrieb Stephen Deasey:
>
> > So, how
> > about assertions?
> >
>
> Good.
>
> So, that means we scratch the idea of putting it in the
> proc/ns_proc syntax and keep it as is, i.e. we parse-out
> only the options
Am 01.06.2005 um 13:24 schrieb Stephen Deasey:
So, how
about assertions?
Good.
So, that means we scratch the idea of putting it in the
proc/ns_proc syntax and keep it as is, i.e. we parse-out
only the options from the argument list and do no extra
type checking there. Type-checking would be
Am 01.06.2005 um 15:45 schrieb Vlad Seryakov:
To be as much close to current Tcl convention in proc syntax we can
add optional type AFTER default value
ns_proc test { {-flag 0 flag} {-list a oneof {a b c}} {-name ""}
{ value "" } } {
}
This way i do not have to remember 2 different ways t
To be as much close to current Tcl convention in proc syntax we can add
optional type AFTER default value
ns_proc test { {-flag 0 flag} {-list a oneof {a b c}} {-name ""} { value
"" } } {
}
This way i do not have to remember 2 different ways to provide default
value and if i want type checki
On 5/30/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 30.05.2005 um 12:23 schrieb Stephen Deasey:
>
> >
> > The other option is -eightbit:flag syntax. It's not perfect, but it's
> > better than nested lists and has ~5 years of usage in the ACS behind
> > it.
> >
>
> Another try (I can'
Am 30.05.2005 um 19:21 schrieb [EMAIL PROTECTED]:
The question is what ns_proc will do if i give wrong type?
Throw error.
Catching all ns_proc calls for exceptions will make code not very
clear?
How typechecks will be enforced?
That is the *exact* reason why you need checks: to throw
ubject: Re: [Re: Re: [naviserver-devel] ns_parseargs example]
Am 30.05.2005 um 12:23 schrieb Stephen Deasey:
>
> The other option is -eightbit:flag syntax. It's not perfect, but it's
> better than nested lists and has ~5 years of usage in the ACS behind
> it.
>
Another t
Am 30.05.2005 um 12:23 schrieb Stephen Deasey:
The other option is -eightbit:flag syntax. It's not perfect, but it's
better than nested lists and has ~5 years of usage in the ACS behind
it.
Another try (I can't just let go) ...
I do not see much sense in trying to keep the Tcl argument lis
Am 30.05.2005 um 12:23 schrieb Stephen Deasey:
On 5/28/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
Well, the above example is wrong. It should be:
ns_proc connect {{{-eightbit flag}} {{-speed list ...
Nested lists are clearly unusable.
They are, indeed, but this is the price for
On 5/28/05, Zoran Vasiljevic <[EMAIL PROTECTED]> wrote:
>
> Am 28.05.2005 um 21:01 schrieb [EMAIL PROTECTED]:
>
> > I like this but can it be list instead of oneof
> >
> > ns_proc connect {{-eightbit flag} {{-speed list {1200 2400 4800}}
> > 4800} {port /dev/ttya}}
> >
>
> Of course it can. But
Am 28.05.2005 um 21:01 schrieb [EMAIL PROTECTED]:
I like this but can it be list instead of oneof
ns_proc connect {{-eightbit flag} {{-speed list {1200 2400 4800}}
4800} {port /dev/ttya}}
Of course it can. But Stephen is not very optimistic
about the syntax altogether...
I'm afraid we do
I like this but can it be list instead of oneof
ns_proc connect {{-eightbit flag} {{-speed list {1200 2400 4800}}
4800} {port /dev/ttya}}
Original Message
To: naviserver-devel@lists.sourceforge.net
From: Zoran Vasiljevic
Subject: Re: [naviserver-devel] ns_parseargs example
17 matches
Mail list logo
