well but thats no real argument, is it?

my.x = temp.x;
my.y = temp.y;
my.z = temp.z; //three semicolons

is also the same as:

vec_set(my.x,temp); //one semicolon


Two semicolons got lost ;). We could also say: They are hidden!
Now the question is: Where is the difference between these hidden semicolons, and those, when I would transform commands into a picture and some short lines, that rebuild the code.

I think the idea of a 100 lines prohgram is a very good one for a contest, but it stays unclear what is allowed and what is not, or let's say, what would be fair, and what wouldn't. Obviously one idea behind this contest is, to find ways to shorten code and use optimised commandments, but I couldn't judge for myself where the border between this goal and making unfair tricks is located.

I assume the default commands of 3dgs count as one, so make use of them and save 2 lines ;). I can't speak for JCL, but for what I read it's about making a lite-c code as compact as possible while performing big or complex things.

Apparently the 100 lines rule is still not clear for some reason. When you send your source, we'll run a semicolon counter over your source files and when it counts 100 or less, the entry is accepted. That's it.

Included files from the Gamestudio include folder and code folder don't count, so you can use acknex.h, default.c or the shaders from the code folder if you want.

hihihi (semicolon counter ):

#define eol ;

my.x = temp.x eol
my.y = temp.y eol
my.z = temp.z eol
...

"#define eol ;" counts as 101 semicolons.

don't you know, semicolon counter has ability to understand defines hehe

(from Joozey)
but, mercuryus, since you actually bothered to write your version i'll trust you thought it up independently

i'd love to see someone try to get away with that

here's a hint to all: try not to put any "wink" emoticons -- ie: ; ) (minus the space) -- in your comments in your code. that could be terribly wasteful.

jibb

ooops! Glory goes to Joozey...

I want a cookie!