maybe this is something (double) Dutch? I can't recall this discussion so it might well have been before I was involved. But three spaces is my standard over two decades now....
Joep 2009/9/28 Sebastien Lelong <[email protected]>: > Hi William, > > I agree with you, 3 spaces is weird, never seen that before too. IIRC, > someone said "4 spaces is too much, 2 spaces isn't enough, so 3 spaces is > the correct value"... This indentation rule can produce endless debates, I > guess it's better keep it buried (isn't that you who already tried to open > cans of worms like this ?... :)) > > Seb > > > > > > > > I prefer indentation using real tab char... > > __ > > (\ .-. .-. /_") > \\_//^\\_//^\\_// > `"` `"` `"` > > > > >> >> Dare I ask, how did JALLIB a >> >> rrive at 3 spaces? In 30 years, I've had >> to confirm to many different styles/conventions/standards, but using 3 >> is a first for me. >> >> It is easy enough for me, thanks to the reindent feature of your >> jallib.py >> >> William >> >> >> On Sep 27, 2:08 pm, Sebastien Lelong <[email protected]> >> wrote: >> > We propose standard for Jal code, as there weren't any. As for >> > supporting >> > code, it should follow its own standard. What makes sense for Jal code >> > may >> > not make sense for other language. So for python, indentation should be >> > 4-spaces, as explained in PEP### (can't remember the number...). I tend >> > to >> > indent with tabs, but now Rob has made me come into the right path, >> > jallib.py is now 4-spaces indented. >> > >> > My 2 cents (of Euros, which may have greater value than $$$... :)) >> > >> > Cheers, >> > Seb >> > -- >> > Sébastien Lelonghttp://www.sirloon.nethttp://sirbot.org >> > >> > 2009/9/27 William <[email protected]> >> > >> > >> > >> > >> > >> > > I'm looking forward to hearing the answer for this also-- after all if >> > > we must adhere to 'standards' for JAL code, should the supporting code >> > > have 'standards' also? :-) >> > >> > > William >> > >> > > On Sep 27, 4:07 am, Rob Hamerling <[email protected]> wrote: >> > > > Hi Seb, >> > >> > > > [email protected] wrote: >> > > > > Revision: 1350 >> > > > > Author: robhamerling >> > > > > Date: Sun Sep 27 01:27:22 2009 >> > > > > Log: >> > > > > Made check on mixed case for (pseudo) variables more general. >> > >> > > > >http://code.google.com/p/jallib/source/detail?r=1350 >> > >> > > > > Modified: >> > > > > /trunk/tools/jallib.py >> > >> > > > I was surprised by the long log. It seems the original (before I >> > > > edited >> > > > it) contained tabs, which are replaced by 4 spaces by my editor. I >> > > > hope >> > > > this doesn't disturb your way of working! >> > > > BTW JSG talks about 3 spaces and no tabs. Does that apply to >> > > > JAL-code or >> > > > also to other code? >> > >> > > > Regards, Rob. >> > >> > > > -- >> > > > Rob Hamerling, Vianen, NL (http://www.robh.nl/) >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
