On Mon, Oct 12, 2009 at 10:43 AM, Steven Roussey <[email protected]> wrote: > >> I started porting those Python-specific tests to JS-specific tests. >> It needs 2 more tests: > > I do beg of you, that we work on JS first, before Python... ;)
Huh? The Python versions are done. I started porting them to JS. > Ick, yeah. It is very consistent now though. I have rules set so if > you want a space after the closing parenthesis of a function > definition you can have it, or not have it, etc. The whole of the file > is inside a function definition, yet it is not indented as such, etc. > That one indenting alone made me have to rework various comments and > lines to be less than 80 cols. Do you want me to fix your version? Do > you not want that kind of consistency? Personally, I prefer it since I > can reformat the whole file to my liking (tabs, etc), then reformat it > again before committing. I won't accidentally push tabs in the source, > etc., that way. No, I want the formatting to remain as is, and for all changes to follow the existing style. That is not unreasonable. Try going to any open source project and reformatting the source code -- see what response you get. I can't believe that you can't change your Eclipse settings so the style is maintained, without autoformatting changing everything. If you can't then Eclipse isn't worth using, as there are literally hundreds of free editors that will do this. Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JSON Template" 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/json-template?hl=en -~----------~----~----~----~------~----~------~--~---
