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 -~----------~----~----~----~------~----~------~--~---
