Hello Cygwin. :-) I have been working on static code analysis from a performance perspective, and I recently applied the concept to Shell and Perl scripts. The most basic idea was to look for usages of Unix commands, their combinations with pipes, and stuff like that to which alternatives using Shell built-ins (or Perl functions) could be possible. e.g. Using ((num++)) instead of `expr $num + 1`. In examples where I had "fixed" anti-patterns, there was often a noticeable improvement (mostly realized in the form of faster runtime). I have also written a dirty parser and put together basic "guides" to go about this: http://bsravanin.blogspot.com/search/label/anti-patterns.
Among Cygwin packages, bash-completion has some of the highest programming anti-patterns, but there are various others as well. Does this seem like a useful idea? If it is, what could be a good way of going about implementing it? Thanks, Sravan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
