brackets

Hi, I found some good news for me on http://www.spip.net/en_article3416.html?var_recherche=bracket: "the parantheses and brackets are no longer mandatory: one can thus write #EXPOSE{rouge} instead of [(#EXPOSE{rouge})]"

Does that mean I can delete each [, ], {, and } in my squelettes? (The editor I'm using always creates a linebreak on the encounter of such a character, that's why.)

Some lines before the quote it says on the same page "#EVAL{} will evaluate the PHP expression between brackets". Well, { and } however are not redundant "brackets"? (I would call them "braces" anyway.)

Hi Barnie,

Does that mean I can delete each [, ], {, and } in my squelettes?
(The editor I'm using always creates a linebreak on the encounter of
such a character, that's why.)

For what I know about this, they are no longer mandatory, but it still
works even if you keep using them.

What I'm sure about, indeed, is at least this point : Maybe you can delete
and ( ) but if I were you, I wouldn't touch any { } which are still
mandatory (in declarations such as #URL{page=plan} or
#CHEMIN{inc/your_file} for exemple, or even the one you just listed to
us)

But maybe someone could confirm or cancel what I'm saying ???

Some lines before the quote it says on the same page "#EVAL{} will
evaluate the PHP expression between brackets". Well, { and } however
are not redundant "brackets"? (I would call them "braces" anyway.)

Maybe a translation bugs. For a moment, when i've read "brackets" I first
thought you were speaking about " " (OK I'm French and it's late in the
night here :wink: )

Regards,
Etienne B.

_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en

Some lines before the quote it says on the same page "#EVAL{} will
evaluate the PHP expression between brackets". Well, { and } however
are not redundant "brackets"? (I would call them "braces" anyway.)

...And when asking google translates, "brackets" returns the french
"parenthèses", although the article you've read seems to make a difference
between parentheses and brackets. I don't know who's wrong in this story.
I'll have a look in my dictionnary when i'll be back home.

E.

An important function of the brackets ist, that the content of the brackets is not displayed, when the expression (balise) is empty. #ENV brought a wrong result without brackets in SPIP 1.8x.

May be you can eleminate some brackets, but probably not all.
here an example:
[<strong>(#TITRE)</strong>] if #TITRE is empty, the HTML-Tags are not generated.

The braces have different function to brackets, the are used to give a parameter to a filter.

Regards
Patrick

barnie.de.los.angeles@myrealbox.com wrote:

Hi, I found some good news for me on http://www.spip.net/ en_article3416.html?var_recherche=bracket: "the parantheses and brackets are no longer mandatory: one can thus write #EXPOSE{rouge} instead of [(#EXPOSE{rouge})]"

Does that mean I can delete each [, ], {, and } in my squelettes? (The editor I'm using always creates a linebreak on the encounter of such a character, that's why.)

Some lines before the quote it says on the same page "#EVAL{} will evaluate the PHP expression between brackets". Well, { and } however are not redundant "brackets"? (I would call them "braces" anyway.)

_______________________________________________
spip-en@rezo.net - http://listes.rezo.net/mailman/listinfo/spip-en