Nocog

Wednesday 27 April 2005

Larry Hastings uses Cog, but worries about missing new files that need to be Cog’ged. To solve the problem, he wrote Nocog. As he describes it, “Nocog scans over its input files, and if any of them contain Cog code, it prints an error and returns -1. If none of them contain any Cog code, it prints nothing and returns 0.”

This isn’t a problem I’ve encountered, but I understand the impulse: the more that code can detect its own problems, the fewer problems will persist. This applies even to builds.

Comments

Add a comment:

Ignore this:
Leave this empty:
Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.
Don't put anything here:
Leave this empty:
URLs auto-link and some tags are allowed: <a><b><i><p><br><pre>.