# Are tokenized PostScript/GhostScript answers acceptable?

I'm not sure how to deal with this answer. That's the shorter code at this time, so it may be the winner.

On one hand, the tokenized version is sort of compressed code, but it seems to be totally unreadable by an human. So I'm not sure if counting the characters of the tokenized version is fair. On the other hand, it's a feature from the language so it doesn't break any rule.

What do you think? Are there other languages which can be compressed on similar ways?

I haven't seen this discussion on meta yet so I'm posting it, it may be useful if somebody asks the same thing.

• I started a similar discussion in chat a few days ago, which you might want to read. I was mostly worried that if we allow this, by extension, compiled or zipped code sizes might be valid, too. – Martin Ender May 13 '14 at 20:08

Despite being a moderator, I'm not speaking for the whole site in this instance. I am just speaking as a user.

I consider that valid. It's not required for the code to be human-readable. We allow submissions in GolfScript or object code, after all.

• Even if I don't know the GolfScript syntax, I can read it when code is posted in a answer. With tokenized PostScript/GhostScript, it can't be displayed as plain text, it's necessary to use hexdump. – A.L May 13 '14 at 19:42
• @n.1, I've posted quite a few GolfScript answers which had to be encoded by hexdump because they use non-printing characters in strings. – Peter Taylor May 13 '14 at 22:04
• @PeterTaylor should we require answers to use printable characters only? – John Dvorak May 14 '14 at 6:25
• @JanDvorak, I don't think so. If the standard interpreter treats ? as \u0004 then a golfer would be crazy not to exploit that. Similarly where the standard interpreter provides aliases for keywords, so Chris' analogy is a good one. – Peter Taylor May 14 '14 at 7:29