Paul,
Not really. Currently there are unnecessary tags used in the templates such
<%body_table%> and
<%/body_table%>, right?
Yes are right, user would not need to add extra tags, because these are already used in original templates...
The bottom line... No, there are no need to place extra tags into your template, and No there will be no need to parse anything 2x.
In addition I suggested global tag parsing as an option (you can turn it on-off), so if you really hate to place tags into globals, just turn off this option... Or even better, if the default option value is to be turned off.
Yes of course.
Because:
a) once there is a need to put something into a global, the global needs a global tag. Now we already have the <%body_table%> tags, so we do not need to add them.
b) once we have a global tag, and we would like to place some tags into that global, we should able to place it there. Therefore global would be need to be parsed for tags (only if global template tag option is turned on).
Are you asking seriously?
Perl globals have the exact syntax... Perl globals Must have the following format:
sub { your code }
So why is a problem for you, to distinguish between perl globals and non-perl globals?
Paul, my opinion is still the same: I think, it is a good idea to implement this feature as I suggested.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
Quote:
Yeah but in order for the global to be processed you need to put a tag in your template...there is parse number one.....<%body_table%> and
<%/body_table%>, right?
Yes are right, user would not need to add extra tags, because these are already used in original templates...
The bottom line... No, there are no need to place extra tags into your template, and No there will be no need to parse anything 2x.
In addition I suggested global tag parsing as an option (you can turn it on-off), so if you really hate to place tags into globals, just turn off this option...
Or even better, if the default option value is to be turned off. Quote:
then you are suggesting putting tags into the global which need to be parsed...there is parse number two.Because:
a) once there is a need to put something into a global, the global needs a global tag. Now we already have the <%body_table%> tags, so we do not need to add them.
b) once we have a global tag, and we would like to place some tags into that global, we should able to place it there. Therefore global would be need to be parsed for tags (only if global template tag option is turned on).
Quote:
Also how are you going to distinguish between perl globals that don't need parsing and non-perl globals that do?Perl globals have the exact syntax... Perl globals Must have the following format:
sub { your code }
So why is a problem for you, to distinguish between perl globals and non-perl globals?
Paul, my opinion is still the same: I think, it is a good idea to implement this feature as I suggested.
Best regards,
Webmaster33
Paid Support from Webmaster33. Expert in Perl programming & Gossamer Threads applications. (click here for prices)
Webmaster33's products (upd.2004.09.26) | Private message | Contact me | Was my post helpful? Donate my help...
