Re^4: Multiple and Nested <FORM>s in CGI

I'm really just trying to understand somebody else's code and understand why they'd use multiple FORMs on a page. I'd like to follow the same coding style as has already been used the project, unless it's a bad idea. (Other than the project's coding standard of including no comments whatsoever...&smiley; )

It appears to me that one big drawback to multiple forms is that params from the other FORMs don't persist. I want to make sure that this really is a drawback, and there isn't an obvious, easy workaround. I'm also fishing to see if there's some advantage to having multiple FORMs – some advantage that's completely escaped me so far.

Comment on Re^4: Multiple and Nested <FORM>s in CGI - HTML

Replies are listed 'Best First'.
Re^5: Multiple and Nested <FORM>s in CGI - HTML by technojosh (Priest) on Aug 17, 2007 at 20:30 UTC
'no comments whatsoever' is never fun when you are digging through someone else's code. Do these multiple forms actually point to different actions? I am just trying to, like you, wrap my head around this... Perhaps, if you want to post some form of the code, maybe I can help understand? (as much as possible on a friday evening anyway...) Edit - just re-read in the OP that they do have different actions...still, if you respond before I head out for the night perhaps I can help...	[reply]
Re^5: Multiple and Nested <FORM>s in CGI - HTML by Anonymous Monk on Aug 18, 2007 at 11:24 UTC
The benefit is modularity, take perlmonks for example, each component is standalone, you just drop it in.	[reply]