format PrettyCCode.hs

[albertnetymk]

camel_str='sub fun { ($var) = @_[0]; return $var if $var =~ /^[A-Z]/; $var =~ s/(?<=[a-z])_(\w)/\u$1/g; return $var; }; next if $_ =~ /^ *--/; s!((?<=[^"\w])|(?<=^))([\w_]+?)((?=[^"\w])|(?=$))!fun($2)!ge'
camel() { perl -pe $camel_str $@ }
camel_i() { perl -pi -e $camel_str $@ }
find ./src -type f -name '*.hs' | xargs zsh -i -c 'camel_i $@'

First commit is built using above scirpt; second commit is built by manually change the indentation.

[kikofernandez]

why? isn't easier to just not write camel case?

[albertnetymk]

Maybe the title is a bit misleading. Apparently, there's sth missing from the last PR on this issue. The scripts are the ones I used to construct this PR.

[kikofernandez]

Ok I understand now. I will review this today

[kikofernandez]

the script is pretty good but cannot deal with indentation issues, such as here, where the indentation is off by one char.

[kaeluka]

Thank you, @albertnetymk!

[kaeluka]

I assigned this to @kikofernandez, as he said he'd review.

[albertnetymk]

The indentation is off-by-one, but still valid. It's not fixed on purpose, so that manual-editing and auto-editing is not mixed together.

[kaeluka]

You can make a second commit for the manual editing.

[kikofernandez]

@albertnetymk I have been told (by @EliasC) to fix indentation issues many many times. I don't see why this should be different if we have spot it on time (before a merge). I agree with @kaeluka , create then a second commit with the right title.

[kaeluka]

Awesome! :) <3