Printable View
Alright, so I have to ask. Do you guys select a highlighting scheme which highlights standard function calls? I am asking this obviously because of the new color coding scheme that had been implemented.
The only thing I have ever really used was VS's default scheme which is the pre-processor, primitive type, keyword, and comment scheme(standard off-red, blue, and green).
I am rather surprised to see malloc highlighted. Is this the norm out there in the professional community?
I believe it's highlighting standard C function names.Mmmmyep.Code:#include<stdio.h>
#include<stdlib.h>
int main( void )
{
char *world,a,b,c,d,e,f;
printf( "hello" );
world = realloc( malloc( 1 ), scanf( "%c%c%c%c%c%c", &a, &b, &c, &d, &e, &f ) );
world[0]=a;
world[1]=b;
world[2]=c;
world[3]=d;
world[4]=e;
world[5]=f;
puts( world );
free( world );
return 0;
}
Quzah.
Trust me... there is *nothing* normal about the professional community of programmers...Quote:
Originally Posted by AndrewHunter
(An analogy to "herding cats" comes immediately to mind.)
LOL.....too much. I guess I was already thinking that when I asked the question; I am just so "amazed" by the code coloring scheme I had to ask......:biggrin:Quote:
Originally Posted by CommonTater
<fogey>
Well those of us "of a certain age" who learned to program on monochrome green-on-black simply don't understand what all the fuss is about.
</fogey>
I mean, every so often, someone wanders in with a code problem which is obviously down to an unterminated quote or comment, yet the glaring slab of colour in the IDE STILL wasn't enough for them to figure it out.
Knowing how to program works - not the palette of wax crayons you use to draw your pretty pictures with.
TTL green, amber or white. <3
Quzah.
Well, I saw that, but really only got into it with the white and blue of DOS EDIT. Now, this all crazy coloring scheme is killing me though and all I was wondering is what you "pros" have set. I really don't see a value in highlighting library calls,since although defined by the standard are technically extensions to the language in the pure sense. I do see a teaching an "glance debugging" value in the VS default red - green - blue coloring scheme.Quote:
Originally Posted by Salem
I just can't seem to get a good color scheem for notepad++ no matter how I try.
Quzah.
I have been missing your responses and I am not sure why. Yep, that is what I am talking about and have learned to rely on. Hence the scheme I picked for the highlighter I made for posting here.Quote:
Originally Posted by quzah
The parser I made just called out "red" "green" and "blue". I was just looking into backhighlighting when we shifted to the auto color feature.Quote:
Originally Posted by quzah
Are you scripting your "rainbows" right now?
That's a distinct possibility. It's what happens when I'm really bored.Quote:
Originally Posted by AndrewHunter
Quzah.
Haha...sounds like a new game I will revisit next time I am "bored". :wink:Quote:
Originally Posted by quzah
Over the years I've been reducing more and more the scope and intensity of my code coloring scheme. Today it mostly boils down to keywords, user-defined objects and strings (I don't even color code symbols anymore). Each live on a different color, but always washed out colors with little visual impact. Admittedly because of the rules and semantics of certain programming language I may feel inclined to add a few elements to that short list. On C# for instance, it could be useful to separate classes from structs so you know exactly what kind of memory management the object you are working with uses.Quote:
Originally Posted by AndrewHunter
Overall though I've been finding more value in less color scheming. I do still believe in it though. Make no mistake. But I just think that, at least for me, it works best as subliminal hint system and as an anti-bug precautionary measure. And I'm not anymore after the aesthetics.
Also, very recently I finally dropped the black background for good. I couldn't find a justification for it anymore. Non emissive, non flick, LCD screens just don't make white so tiring to the eyes anymore. But also, with a black background is harder to go for a suave color scheme: Black background tends to increase contrast with the overall text color, which is a fatigue factor in itself (although, of course, not so tiring as white was on CRT screens). At the same time it reduces the contrast between similar colors, making it harder to produce suave color schemes without increasing contrast with the background. White background (or slightly grey, as I personally use it) makes it much easier to produce text that stands out, that is clear, and that doesn't tire your eyes or brain.
Or at least that's how it has been working for me.
Y'know what... I often find mistakes because something is "the wrong color"... Spelling, open ended quotes, etc. I won't say I couldn't do without it, but syntax highlighting has been a real help. The value in highlighting library calls is you can see your typos when they fail to color coordinate with Quzah's latest dance ensemble.Quote:
Originally Posted by AndrewHunter
I just have been using the intelli-sense feature in the IDE to quickly identify the typos and mismatched braces / arguments. I can see the value in it for those who don't like that feature / don't use an IDE with it.Quote:
Originally Posted by CommonTater
LOL....he has become quite dazzling lately. Are we invited to your "coming out" party quzah?Quote:
Originally Posted by CommonTater