CMegaC: give me a signed 8-bit integer bigger than 127.

now for a regular one

128

@mousetail it’s a signed 8 bit integer.

128 is signed

CMC: write a program that can read what was written to STDOUT when inserted in another program.

@mousetail it’s a signed 8-bit integer

greycoded?

@mousetail What is greycoding

@Iamkindofalanguagedev −120

@mousetail no not greycoded.

@Adám I was thinking -128, but that works as well.

@Iamkindofalanguagedev APL: ⍞

@Iamkindofalanguagedev 128, which in excess-1 is written with the bit pattern 11111111

CMC: print this ascii art:

  +--------------  +-+                   +-+   +--------------  |
 ++                | |                   | |  ++                |
 |                 |  \                  / |  |                 |
 |                 |   \                /  |  |                 |
 |                 |    \              /   |  |                 |
 |                 |     \            /    |  |                 |
 |                 |      \          /     |  |                 |
 |                 |       \        /      |  |                 |

@Iamkindofalanguagedev what is it? I can't see it on my phone

@Simd Large capital letters CMC, basically

@Iamkindofalanguagedev Just reposting it doesn't help on a 32-character-wide screen

It looks more like 'OV' than 'CMC' on my phone, for instance

@Iamkindofalanguagedev obviously cheating, but: fetch('chat.stackexchange.com/messages/240/64044420').then(x=>x.text()).then(alert)

@DLosc thanks

Comment I just found:

# Now, you could do something like the below instead, and it works
# fine and is more direct... except that for no clear reason, it
# is extremely slow and much more memory hungry.  In particular,
# despite using identical format and options, it is somewhere
# around 40-80 times slower than this function, and uses somewhere
# around 2-6 times as much memory.
#
# I have no explanation whatsoever for this.

@RubenVerg do it

@Bubbler Taking a break for now, but I just wanted to share that I'm on the home stretch. Thank you for your advice (Edit: I had a link here but chat markdown broke it, so I'm removing it)

I'm encoding it in base-95 (not 96 because there's no spaces)

Is that a quine?

it will be

Cool

= isn't a valid opcode. I'm using it to mark characters that are never interpreted, so I'm free to make them whatever makes the data section shortest

The first ! is never hit, for example, and iirc I get a 3-byte rather than 4-byte UTF-8 character by using ! rather than a higher opcode

The '8 at the end is the length of the data section, right now it becomes "<unprintable> but I have a feeling the data section will become long enough that it won't be unprintable anymore

Okay problem: The code had been written assuming the value of the NOP sled could be pushed in one byte (i.e. no more than 127), and it can't. I have to restructure some of the code but it's not a huge deal

Ah. The bottom row will be 92 characters long. And the size of the NOP slide grows in proportion to the square of that

So this is a viable approach but not a short one