This came up in the Python 3 thread, but I just wanted to note that I was called out for this when I tried to model a hemisphere by modeling the path of a cutting tool so as to cut it out, so yeah, there is such a thing.
Don't try this at home, it resulted in simply glacial performance and wasn't usable, which is unfortunate, since I'd really like a nicer tool than CAMotics to model subtractive 3D CAM in.
As I've linked before, there are an awful lot of programmatic CAD tools, and FWIW, I find OpenSCAD the most generally workable and useful, and I greatly appreciate it, and the efforts of the developers.
William

At first, I thought someone had noticed that I recently named a module
butthole(). It's for a hand tool handle, and it has a module which does the
hole for hanging the tool, which is in the butt of the handle (yes, it also
has a butt() module...). I didn't even realize it, it was half an hour later
that I noticed it.

But, jokes aside, yep, it's a great tool. It has some rough edges, but the
solution is to polish, not to dump and rewrite. I've also found that, most
of the time when something is slow, I'm not doing it the smart way...

--
Sent from: http://forum.openscad.org/

Those moments when we push the envelope beyond our skills, look on at at the
resulting glacier in bitter disappointment, then tweak, polish or start from
scratch and learn stuff.

There are no “(in)appropriate” uses of an engineering software, just
inappropriate responses to the results. Mistakes can make us better.

And butthole() lol, the cover to hide the nut holding the handle on the
butt() could aslo be the buttplug() :-D

Make things, travel and tell stories.

Sent from: http://forum.openscad.org/