hi, i just finished a little project (finished means working, not secure. it actually is a bit quick'n'dirty because i'm tired) called "code normaliser" that takes a norms file and a source file/directory and applies these norms to the sources. the norms file consists of lines of this scheme: start-of-block (regexp), end-of-block (regexp), indentation (integer) and describes how to indent parts of the source. (my personal one is included) there are other formatting things directly in the code of the program like eliminating unnecessary spaces, empty lines or adjusting comments and adding empty lines after specific parts of the source. it is *very very* personalised because i wrote it for someone writing a book about gambas, the source samples have to be standardised in a way we together thought, it would look well. so if somebody - like a "formatting nazi" ;) - would like to have a look at it or try it out, i'll attach the source archive.
regards, tobi ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Gambas-user mailing list Gambas-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gambas-user
