FUNCTIONCALL vs VARIABLE html tags
Posted: Thu Oct 22, 2009 8:25 am
I can see merits to the FUNCTIONCALL tag where the VARIABLE tag isn't needed to permit
passing an argument. When the only intent is to get something done like setting the post
handler, the name is certainly more descriptive. When you don't intend to use the feature of
automatically generating page text, you don't have to return a pointer to an empty string. A
colleague suggests that we just standardize on using VARIABLE always, since we are unlikely to use the feature of passing info to the function in the URL using the ? suffix. My question is if there is any overhead advantage to one tag or the other: size of generated flash image, execution time, RAM/stack usage, etc. I'd also like to verify that there are no other considerations. Although I don't think it likely that either tag would be deprecated in the future, that would be a good example of what I mean by "other" considerations.
passing an argument. When the only intent is to get something done like setting the post
handler, the name is certainly more descriptive. When you don't intend to use the feature of
automatically generating page text, you don't have to return a pointer to an empty string. A
colleague suggests that we just standardize on using VARIABLE always, since we are unlikely to use the feature of passing info to the function in the URL using the ? suffix. My question is if there is any overhead advantage to one tag or the other: size of generated flash image, execution time, RAM/stack usage, etc. I'd also like to verify that there are no other considerations. Although I don't think it likely that either tag would be deprecated in the future, that would be a good example of what I mean by "other" considerations.