Support and General Use > Theming and Appearance Customization

two minor comment handling changes

<< < (4/4)

ZincAlloy:

--- Quote from: JdGordon on September 09, 2009, 04:55:26 PM ---That code snippet is what I'd like to discourage... the same could (and imo *should*) be done using blank lines... using comment lines makes it harder to read.

--- End quote ---

I believe comment lines make it easier to read. changing that behaviour will not make lazy theme authors document their work.

JdGordon:
this has been discussed in IRC for the last while and ths is the general consensus....

comments on their own line eat the \n - no change from svn
comments at the end of the line eat *dont* eat the \n - changed from svn
a new control char should be used to join lines, discussing which to use now, and how they can work if they are before the inline comment or not

pixelma:
After the first few lines in IRC, I found out that I misunderstood and was misunderstood...

I thought that the patch would also change the behaviour of full-line comments (starting with #) which are currently ignored and won't add blank lines, so my code snippet was there to demonstrate that all WPSs that already use those would be semi-broken if this behaviour of full-line comments was changed. I did not want to say that I want to use these pure comment lines to "add" blank lines - not at all.

Angus_NB:

--- Quote from: gevaerts on September 09, 2009, 03:51:11 PM ---
--- Quote from: Angus_NB on September 09, 2009, 03:37:24 PM ---Some programming languages, Visual Basic, VBA, use the _ character.

--- End quote ---
And what if you want a literal '_' character at the end of a line?

--- End quote ---
You would do the same as any other character, put two in a row.  ie: _ _ or %%
I am not arguing for or against the _ character.  I don't care what is used as long as it's documented.  I would probably have each line start with a # as it is now.

Navigation

[0] Message Index

[*] Previous page