Reserved identifiers in C

You aren't supposed to create identifiers that match these patterns, if you're trying to write portable, future-proof C code. But you probably are. We all are.

Because these rules aren't nice, and you won't be warned that you've broken one.

Is it worth it?

Adapted from

Cosmopolitan C Library: "build-once run-anywhere c without devops"

Purports to create small ~40kb executables that run on Linux, Mac, Windows, FreeBSD, and OpenBSD. In the same binary.

"Zen and the Art of Resource Editing, Fourth Edition" foreword, written by... ?!

12" cover art I did for a friend's single. Trance.

Part of an all-original, free content pack for DDR-like, released yesterday.

@tehn I've had this guy since 2007 :) Followed me here to Tokyo.

@neauoire I noticed the headers in the readme markdown file on for orca don't display the code spans as intended (right is GitHub.)

I traced two of the of the peanut people doodles from @rek 's amazing North Pacific logbook so that I could put them on my desktop

Read the logbook here:

Exasperated by Qt's buggy/janky built-in platform agnostic style engine, for my commercial software project ( ), I wrote a new Qt style engine, Phantom, and also released it as open source:

The open source KeePassXC project has released version 2.6.0, which uses the Phantom code for their new cross-platform theme:

Show older

Merveilles is a community project aimed at the establishment of new ways of speaking, seeing and organizing information — A culture that seeks augmentation through the arts of engineering and design. A warm welcome to any like-minded people who feel these ideals resonate with them.