--
tour.google.com has syntax highlighting.Usually I prefer to use the tour instead of "play" just because of this.
--
But as far as I can see there's not syntax highlighting there either.
-christoph--
'gofmt -v' would automatically insert the right ANSI terminal color escape sequences into the source code to make it visually appealing. This might be material for a future Go++.
Or even better, .goxy files, which add to that a more Java-like syntax and automatic conversion from an exception syntax into panic with json-encoded strings and also generic syntax. Of course the result is so unwieldy that you need an eclipse-like IDE to keep track of everything, which will need another layer of "gen" metadata to hold information about generic dependencies.
It seems a lot, but I think with the resulting .goxygen files we will finally be able to breathe easier.
Thomas
--
--
Making my font huge isn't always an option.
The most relavent highlight for me is making all := declarations another color, mainly because I'm very farsighted and sometimes I miss the little colon even with glasses on. I think SH has importance to other people with poor vision as well, as an accessibility feature. Color schemes aren't important as long as they're high contrast.Making my font huge isn't always an option.
--
I loved Cuisenaire rods! Wow, haven't thought about them in like 35 years....
My own use case has always been crappy "commercial grade" code written with IDEs and terminals of 200 glyphs wide. Heavy use of ifdef at multiple levels and stuff like code embedded in other languages code (e.g. templates) are the norm.
Add DSLs and the meriad of unix config file languages to the mix and I will proudly confess, that I don't know all those grammars well enough and don't even want to. So I let my editor identify things like keywords, bad white space (Makefiles, Python, shell), strings, escape sequences, comment paragraphs, embedded code fragments in templates and ifdefed out code.
Found many bugs directly after opening the editor while more senior people stared hours at it.
Call me retarded idiot, but it just saved me and my colleagues a lot of time during the last 25 years of coding :-)
Well, this is a topic on which people will never reach consensus.So I prefer to look for my favorite editors rather than fight over it.
--
Hey, I was quoting the Bible. If that's degrading, I guess I'm done.
-rob
--
Looks like you hit a nerve. I wonder what color it was...
--
Yes, his comments where meant to be degrading -- no matter what their
source and original context. I, approaching my 40th year, am truly
a child compared to the venerable Mr. Pike. The statements say more
about his age than they do about mine. Far from being insulted, I am
a little depressed that a giant such as Mr. Pike has reached an age
when he dismisses ideas, less from their merit, than based on his own
long-ingrained habits and nostalgia.