On Sun, Sep 13, 2009 at 8:29 AM, Manu Abraham wrote: > There's even a war on tabs vs spaces. But strictly > speaking it becomes a nightmare with spaces, when you are dealing with > a SCM. This comes to play, when you want to look at what you have > changed on a piece of code over time on a specific file or project. > For small < 500 lines of code this doesn't matter, but for larger code > sets this does really matter. > I guess you mean "white space" when you say "space". With most source control system you have an option to switch off white space checking when making the diff on different versions or branch of the source tree, so it should not be matter. Anyway, sharing a code here in piclist the problem mostly occurs when someone just blindly insert the code as a normal text into the mail body. Many of the mail clients just chops off the leading spaces or tabs and also the text style is in normal mode which means using a proportional typeface font. I do not know what would be the best practice to do but this pastebin site is generally not a good idea as it is not getting archived on either on the client side nor on any of the piclist's mirrors. Maybe an attachment would be sufficient? Tamas > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- http://www.mcuhobby.com -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist