Deb Lewis
2006-Oct-17 12:53 UTC
[Masterview-devel] Code review: adding parens in generated output erb
I think the resulting expressions using paren''d function notation is fine. But.. it''s a bit odd to see "if( foo )" and "elseif( bar )" without a space, though it does seem to parse correctly. Dunno if it''s worth adding a special-case check for conditional keywords vs. function name in prepare_output. ~ Deb
Jeff Barczewski
2006-Oct-17 15:07 UTC
[Masterview-devel] Code review: adding parens in generated output erb
Great. Well personally when I use the parens with conditionals I usually do it without the space (like it is), but we can do something special if you think it is necessary, otherwise I think simple is good. Jeff On 10/17/06, Deb Lewis <djlewis at acm.org> wrote:> I think the resulting expressions using paren''d function notation is fine. > > But.. it''s a bit odd to see "if( foo )" and "elseif( bar )" without a space, > though it does seem to parse correctly. Dunno if it''s worth adding a > special-case check for conditional keywords vs. function name in > prepare_output. > > ~ Deb > > > _______________________________________________ > Masterview-devel mailing list > Masterview-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/masterview-devel >
Deb Lewis
2006-Oct-17 16:37 UTC
[Masterview-devel] Code review: adding parens in generated output erb
>>> personally when I use the parens with conditionals >> I usually do it without the space (like it is)reeaally???? wow, ok then. I never do and questioned whether it was even syntactically legal when I saw that notation in the test cases. as long as it compiles and executes correctly, leave it be. ~ Deb