>
>
>
>
> [+ $set[$row]{name} +]
>
>
>
>
>
> If I submit this form, $fdat{foo} will contain a tab-separated string
> of 'Y' and '' values.
> However when I do this, all the input fields will have a 'checked' in
> them.
It doesn't look for the first value, but for the value attribute. So th
>
> That would be much better. But it does introduce a new kind of tag
> that wraps around other tags. I don't know whether that would
> complicate your parser.
>
Embperl 2.0 parser can handle this with just a few lines more in the syntax
definition, I am not sure if I will introduce it in 1.3.
On Sun, Mar 25, 2001 at 01:54:05PM +0200, Gerald Richter wrote:
> >
> > I don't have any great ideas here. The only thing I've come up with
> > so far is that you could have a variation on [+ +] which
> > conditionally affected the line. Let's call it [? ?].
> > [? $foo ?],
> > would result in e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At 1:54 PM +0200 3/25/01, Gerald Richter wrote:
>[? [+ $foo +], ?]
>
>which will do actualy the same, but display everything between [? ?] or
>nothing
That would be much better. But it does introduce a new kind of tag
that wraps around other tags.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[+ $set[$row]{name} +]
If I submit this form, $fdat{foo} will contain a tab-separated string
of 'Y' and '' values.
However when I do this, all the input fields will have a 'checked' in
them. I suspect it's keying off the fir
Hi,
you could add more variables (or better to say hash keys). There maybe
another problem with your code.
If you are using Embperl, it's easier to use Embperl buildin session
management (which also uses Apache::Session), but provides the setup for
you. If you don't use Embperl, you are on the w
>
> I don't have any great ideas here. The only thing I've come up with
> so far is that you could have a variation on [+ +] which
> conditionally affected the line. Let's call it [? ?].
> [? $foo ?],
> would result in either
> something,
> or no line at all.
What I don't like at this idea that
