Miscellaneous - Forum

Museum of code Disease

Anonymous — Tue, 12 Aug 2025 22:02:56 +0000

Hi all,

I created a collection of intentionally AWFUL code examples to educate anti-patterns through humor!

Each "exhibit" has:

- Nightmare file: Maximum chaos (for example, `#define TRUE FALSE`),
- Autopsy file: Educational commentary explaining the disasters,

Perfect for code review training and learning what NOT to do!

WARNING: DO NOT USE IN PRODUCTION!

https://github.com/ikelaiah/museum-of-code-disease

Thanks,
Iwan

macOS - How to determine minimum OS version requirement for an executabe

Hans — Sun, 07 Jan 2024 17:59:22 +0000

Just something I needed to know while trying to find why Lazarus no longer observed dark mode under macOS.

Seems this may be SDK version related, so I tried to figure out what the minimum macOS version requirements where for certain applications.

The newer way (binfilename = the filename of your executable):

otool -l binfilename | grep minos

For older macOS versions (I presume before Big Sur):

otool -l binfilename | grep -A 3 LC_VERSION_MIN_MACOSX

macOS - Determine Xcode command tools version in Terminal

Hans — Wed, 11 Oct 2023 08:04:30 +0000

With all the changes lately, I found it a challenge to determine what version command-line tools I had installed on my Mac.

After all, XCode gives me a rather useless number:

$ xcode-select --version

xcode-select version 2397

But with some help I did find that the CLang version (clang --version) is the indicator we need to look for (now that makes sense, and why is Xcode version not showing this?)

$ clang --version

Apple clang version 15.0.0 (clang-1500.0.40.1)
Target: arm64-apple-darwin22.6.0
Thread model: posix
InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

So there ya go: command line tools 15 ... (in this example)

macOS - How to make a backup of your signing certificates with the help of Xcode

Hans — Wed, 11 Oct 2023 07:43:30 +0000

I'm sure I'm not the only one and I'm a little surprised to see how cumbersome Apple has made it to work with signing certificates.
I use more than 1 Mac to develop software, which need the signing certificates, but I do not use Xcode ... at all. I just cannot stand XCode.

So on one of my computers I have everything setup real nice, so that manual signing works flawless.
Now comes the disaster on how to copy my certificates to my other Mac, and to my surprise Xcode comes to the rescue.
Yes you heard me right; I'm not using Xcode, but I have it installed anyway (SDK's, Command-line tools, signing tools etc come nicely bundled with this).

Backup Certificates:

Start XCode
Go to Xcode menu -> Settings -> Account and select your account.
At the bottom click the dotted circle:

460
Select "Export Apple ID and Code Signing Assets..." which will bundle all this in a single file (password protected).

You may have noticed in step 3 that there is a "Import Apple ID and Code Signing Assets..." option.
You can use this option on the other Mac to import your certificates again.