fix script generation to not comment out the first line

[Ukalnins]

Seems that noone is using the deadlock timer.

[gabebear]

What versions of Xcode has this been tested in? The last time this escaping was tweaked was because of a problem parsing it in Xcode 10 69b24ca.

Since this has broken on Xcode versions before ideally want to test at least:

• Xcode11 on Mojave
• Xcode12 on Catalina
• Xcode12 on Big Sur

I don't have any Mojave Macs anymore, but could check the others if you haven't.

[gabebear]

The multi-nested escaping makes my head hurt.

• XML .pbxproj file containing:
  • bash script containing:
    • both double-quoted and single-quoted strings containing:
      • backslash escaped characters containing:
        • ObjC code containing:
          • Python code.

Is it time to kill this script and the .py file and just check in the .py.h file?

[Ukalnins]

I'm running Xcode-12 on Catalina, so it works on that. I can check Big Sur on monday.

I would be against retiring the separate python script as it simplifies development of the script. Though I agree that the number of nested escaping is complicated and hacky as hell. Maybe splitting it out generation as a separate script help?

[gabebear]

Hmmm... what about switching to raw-literal-strings? C++11(and ObjC++) supports them in this format:

const char* python_script = R"prx63htg4(
import time
import os
import sys
import shlex
import lldb

blah blah...
)prx63htg4";

Swift's """ literal syntax is nice, but has severe drawbacks since the Swift runtime only started shipping in MacOS 10.14.4... SOOOOooo wish ObjC supported them for NSString.

[gabebear]

Going to go ahead and merge rather than overthink it

[Ukalnins]

Hi, sorry, got sick and forgot about this PL.

I really like your idea, we can just put it in a separate cpp file. I'll create a PL when I have the time.

[gabebear]

No worries, thanks for all the hard work!