Tomasz said:
Sure that separation of stable and unstable is nice,
but if test suddenly
becomes, well, real code testing place, shouldn't we make some test2 just
for
playing with random code not necessarily meant for
usage in real
Wikipedias
in predictable future ?
Hey, that's a good idea, why didn't I think of that? Oh, that's right, I
did:
http://test.wikipedia.org/w/tim/wiki.phtml
(actually it wasn't my idea, there was already a directory there called
"magnus-version" and I took my cue from that)
Why not just: "The code should follow whatever is
considered to be
good practice, unless there are reasons to do it some other way".
Wikipedia software isn't any special, so it doesn't need any special
coding rules. And 78 chars / line was important 10 years ago, but is
seriously
too small for year 2003. Come on, we're all using
hardware that easily
allows over 120 chars per line, not ?
And Erik said:
Thomas-
I like sometimes to print a piece of code.
Without reformating it.
But that's what code formatters are for. I'm no fan of hard line breaks --
I have a reasonably large screen, and with all the whitespace that's
necessary for well formatted code, I need to make use of it in order to
make basic constructs visible. IMHO this kind of formatting should be done
dynamically as needed.
I was once scarred by having to convert ~5000 lines of code to an 84 column
limit by hand so that it could be printed, so now I tend to use lots of line
breaks. But if anyone declares that some other style is the "Wikipedia
standard", I'll be happy to conform to it.
-- Tim Starling <ua.ude.bleminu.scisyhp(a)gnilrats.t>