Copyright © 2014,2015 by Thomas E. Dickey
Here are suggested definitions:
- an·si·fy (an′-ze-fī′)
v. an·si·fied, an·si·fy·ing, an·si·fies
- To convert or transform into one of the ANSI-standardized formats.
The ANSI C computer language is generally assumed by context.
ANSI published many standards.
- To convert or transform C programs from K&R syntax to ANSI prototypes.
- To become a standard (ANSI) C program; use function prototypes and other syntax defined in ANSI C.
- To exploit features of ANSI C useful for compiler checks, including function prototypes, the
constkeyword, token concatenation with the preprocessor.
- Acquisition or methodical use of ANSI-standard syntax, as of C computer programs or terminal control sequences.
- The condition of being ansified.
- A set of programs which has been ansified.
I did not coin this term, but found it most appropriate for describing the conversion from K&R C to ANSI C. It is not found in the so-called jargon file; the closest term “ANSI” is helpful only for general background.
The work that I did for XFree86 (referring to email) started in May 1998 (see notes for patch #77). XFree86 3.Ni (October 6, 1998) included these items
1884. Cleanup Xlibint.h, which significantly reduces the level of compiler warnings, and also cleanup XIE's error.h (#2007, Thomas Dickey). 1883. Add support for built-in driver modes (#2006, Egbert Eich). 1882. Ansify and remove gcc warnings for imake, makedepend, lndir, makestrs, makekeys and mkg3states) (#2005, Matthieu Herrb).
Referring again to my email, I see that a few people used the term before I picked it up and reused it. For instance,
ansi2knr, e.g., ANSIfy during 1997 in the
Referring to ANSI C seems to be the most common usage. It may
have been first (or most widely) used relating to
ansi2knr. Here are some additional mentions for that
A quick look at the AT&T yacc parser suggests that it'd be easy enough to ansify it, probably without having to change yacc at all.
If that doesn't work, you might try snarfing the 'ansi2knr.c' program from the jpeg directory, and running it on all the .c and .h files in the tiff directory. It purports to de-ANSIfy C code, and it may do the trick. Again, I don't know how successful you'll be...
Here are some other mentions:
1994-11-02 FranÃ§ois Pinard <email@example.com> * src/freeze.c (produce_frozen_state): If the frozen file cannot be opened, return immediately after producing the error message. Reported by Andreas Schwab. * configure.in: Check for const only after having found possible ANSIfying compiler flags, this is of no use to check it before. Reported by Alexander Lehmann.
Amy A. Lewis firstname.lastname@example.org Mid-October '95 Another utility, ansify, now compiles; it has not been tested at all, so it may not work even slightly. Ansify is a rather stupid program, all things considered, but the work on it does raise an interesting possibility for an enhanced fortune. At present, the fortune databases contain x^Hy sequences for underline and special characters (and this can be extended to include bold, = x^Hx). Ansify is stupid because it doesn't use the proper tools, ie termcap or terminfo (hmmm ... since it works on files, that may not be so stupid); it appears that if that can be done, then a termcap/terminfo enhanced fortune could be produced, which would recognize the existence of ^H in a string and attempt to display using appropriate control sequences. This sort of modification would be of greater interest to casual users, I think, than even the bug fixes, and since it would not force changes in the storage of fortunes, it is eminently portable. Consider this a 'todo' announcement.
print "\n'$self' $version\n\n"; print "Converter for non-standard C comments ('// ...')\n"; print "to ANSI C style comments ('/* ... */')\n\n";
print "\n'$self' $version\n\n"; print "Converter for ANSI C style comments ('/* ... */')\n"; print "to non-standard C comments ('// ...')\n\n";
ANSI terminal controls, in particular for color have been around for a while. Applying the term "ANSIfy" to those seems to be recent.
command-line tool to convert images to ANSI escape
A Ruby script, starting in February 2012.
This tool takes an image from the internet, converts it to 256 colour unicode ANSI art