Calculator Community > Community Contests

Code Golf - The Information/Discussion/Planning Thread

<< < (2/11) > >>

Ivoah:

--- Quote from: Juju on June 05, 2015, 08:54:37 pm ---I think we should also have rules so counting bytes is consistent between challenge creators, like, convert newlines to UNIX style (you can do that in Notepad++ for you Windows users, one newline is one byte) and no ending newline (substract one for you Linux users I guess).

--- End quote ---

I agree

c4ooo:
There are several ways to score an entry that are generally used:
1) size in chars of source code
2) number of bytes of source code
And finally
3) output size in bytes of final compiled/fully runnable  program. (If your language is interpreted, like windows batch, use method 1 or 2, preferable 2)
I think that the host should have a choice as to what scoring method to use. :)

pimathbrainiac:

--- Quote from: c4ooo on June 05, 2015, 09:12:33 pm ---There are several ways to score an entry that are generally used:
1) size in chars of source code
2) number of bytes in source code
And finally
3) output size in bytes of final compiled program.
I think that the host should have a choice as to what scoring method to use. :)

--- End quote ---

I don't think number 3 is a good idea, since some languages have distinct advantages over others in binary size.

Ivoah:

--- Quote from: pimathbrainiac on June 05, 2015, 09:15:13 pm ---
--- Quote from: c4ooo on June 05, 2015, 09:12:33 pm ---There are several ways to score an entry that are generally used:
1) size in chars of source code
2) number of bytes in source code
And finally
3) output size in bytes of final compiled program.
I think that the host should have a choice as to what scoring method to use. :)

--- End quote ---

I don't think number 3 is a good idea, since some languages have distinct advantages over others in binary size.

--- End quote ---

Yeah, #3 sounds like a bad idea (unless it's assembly language).

Juju:
Number 3 is not pratical if we are to mix interpreted and compild languages, unless we accept assembly. For the newlines, the setup I described is the one we used before with JWinslow23 (I think) and is the one that minimizes the number of bytes. Also, for most purposes, we don't use characters above 127, so pretty much every character is 1 byte, although we should count characters.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version