Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

13
  • \$\begingroup\$ @LliwTelracs Huh, the C program linked by Chance in his answer had a different output for the list of tokens: ;#yy;#yy#yy0l0m1k1k0l0i0j0h0h1d0e0b0b0o1d0b0e0e1d0i0f0g0n0n0o0n0c0c0o0f0c0g0g0f0h0j0j0i1k0m0m0l^_()z z()()z; ^_^_ \$\endgroup\$ Commented Feb 1, 2017 at 16:49
  • \$\begingroup\$ The error was that I was copy pasting the value to my program so it couldn't recognize the tabs or escapes \$\endgroup\$ Commented Feb 1, 2017 at 17:25
  • \$\begingroup\$ @LliwTelracs Just trying to figure out the tokenisation myself, it looks like I've now got a semicolon appearing three times. I could add an extra one except that I don't think I can spare the byte as that'll misalign Hexagony. Hmm... \$\endgroup\$ Commented Feb 1, 2017 at 17:57
  • 1
    \$\begingroup\$ Incident works! \$\endgroup\$ Commented Feb 1, 2017 at 21:13
  • 1
    \$\begingroup\$ @Chance I've just been looking at how that first line is valid in the C Preprocessor, it looks like it's the output from the Preprocessor used for debug info etc. It means "now returning (2) to file with name "16" line 1". I think it's the 2 that makes Clang choke (and gcc warn) since it never went into any files in the first place, so there's nothing to return from. When I get the chance I might experiment with changing it to something else to make it compile in Clang too. See gcc.gnu.org/onlinedocs/cpp/… \$\endgroup\$ Commented Feb 2, 2017 at 12:07