#5 Allow for setting line separator for output
Even though Backslash works in Jamon 2.3 with Windows to remove a directive line, if you create some .jamon files on a *nix box and others on a windows box then generate code on either platform, you get different results because of the hardcoded line separators.
The symptom is that files have extra empty lines in them. The headache is for unit testing. Having sample text files to check output against is difficult unless all the .jamon files and text files have the same line separators throughout.
I suggest adding an option to force the output to use a particular line separator. This would reduce my headaches. At this point, most of my .jamon files were created on a linux box, but a few were done with windows. And since we have a mix of linux and windows boxes on which these are created, I am resorting to an editor to set the line separators to linux style on the windows boxes so everything is consistent.
I suggest adding a directive as below. Just a suggestion...
force *nix style
<%lineseparator #n>
force windows style
<%lineseparator #rn>
force mac style
<%lineseparator #r>
In the generated code I think it should probably still hardcode the line separator for backwards compatibility.
Discussion
Anonymous
