1.) the type of a variable is distributed to all following variables seperated by commas... however, if it is a pointer, the, er, pointosity of it, is not distributed... [it's kinda annoying... but can be averted...]
2.) C/++ does not have conventions for repassing a variable argument list without having to parse it yourself!!! so, essentially, you can't integrate formatted console output in your own text-spewing functions!!! argh!!! [std argX inclusion here...]
Hmm...Program your own compiler and base it on C++...Call it C++++! With just 2 edits to it. :D
damn straight!
I will be waiting for you "completion" of your "C++++"
---------------
Engineer223
uhh... hehe, nevermind, i figured out the second one and i'm high as a kite... but the first one still might possibly be of some sort of possibly adjectivized as minor if that annoyance...
Then do a C+=2 to fix the first problem!
Have you noticed that if you draw the 4 "+"'s in two rows of two above each other you get C#, (use a little imagination).
gasp!... does that mean that C# has conventions for all this? that would be a weird coincidence thingy... good say adrianxw!
>the type of a variable is distributed to all following
> variables seperated by commas
MY coding convention says: "one variable, one line."
no problems here ;)
>C/++ does not have conventions for repassing a variable >argument list without having to parse it yourself!!!
hum... yes, it does. I'm too lazy to post, but maybe I will look it up later. I think someone already mentioned it in your thread...
>>one variable, one line
Amen...Also looks better too!
what?! pysch! whatever... you can align the variable declarations to allow easy traversing of variable names using a one-poly method... if cursor-past-end'o'line is enabled [if you have it] you can traverse the white space to no limits of the imagination... making more useful commentary as well!
>>> MY coding convention says: "one variable, one line."
Always, always, always.
>>> MY coding convention says: "one variable, one line."
Sometimes I use that, but if I'm doing something with graphics or loop variables, I always just go
double x,y,z;
but if I'm doing something else I do em on different lines...unless there are a lot....lol.
you and whose army? is this something i, of all programmers in the universe, did not know about which was a defacto type deal? hmm? hmmm?!?!Quote:
Always, always, always.
>>> you and whose army?
Me, and every quality/standards department in any professional house I have ever worked in.
You said it yourself, with pointers in particular, it can lead to traps/misunderstandings/cockups, especially when there are less experienced/junior/trainee programmers on the team.
You don't do it, you don't have the trap to fall into. Professional.
what about non-pointers? where the distribution is even and straight-forward? why would C/++ be standardized to allow this if it wasn't professional? etc...