History log of /openbsd-current/usr.bin/lex/filter.c
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: OPENBSD_6_2_BASE
# 1.9 30-Aug-2017 lteo

Remove unused variable; no binary change.

From Michael W. Bombardieri, thanks!


# 1.8 17-Aug-2017 tedu

combine malloc/memset into calloc. from Michael W. Bombardieri


Revision tags: OPENBSD_6_1_BASE
# 1.7 18-Dec-2016 krw

Nuke more unused variables.

ok millert@


Revision tags: OPENBSD_5_9_BASE OPENBSD_6_0_BASE
# 1.6 19-Nov-2015 tedu

it is not necessary to cast the result of malloc/calloc.
also replace some 0s with the modern concept of NULL


# 1.5 19-Nov-2015 tedu

flex_alloc and flex_free are nothing more than malloc and free, so replace
them with the real functions so as to not trick people into thinking they
are special


# 1.4 19-Nov-2015 tedu

orbital strike from moonbase knf


# 1.3 19-Nov-2015 tedu

repair some of the preposterously damaged indentation


# 1.2 19-Nov-2015 tedu

we don't keep vim modelines in files


# 1.1 19-Nov-2015 tedu

Update flex from ancient 2.5.4 to the recent 2.5.39.
This work was all done by Serguey Parkhomovsky. Thanks.
Some changes from upstream:
* Removed autotools cruft/localization/texinfo manual/etc
* Kept the old manpage, as the new manpage is content-free
* Used safe string handling functions and fixed several compiler warnings
* pledge(2). Flex 2.5.39 now forks/execs its filter chains and needs proc
exec in addition to what was previously pledged
* Removed register keyword from all variable declarations
* renamed parse.c, parse.h, scan.c, skel.c with init prefix so compiling
flex outside of obj by accident wouldn't clobber the bootstrap files
* Minor fixes (spelling, accessing buf[strlen(buf) - 1] for zero-length
strings in initscan.c/scan.l, etc) that were already in our tree

This is a huge change, so it's going in the tree code bomb style.
I'm not excited about the growth in complexity (like now running m4
to _post_ process lexers) but hopefully this will be a one time update
and we will now take "ownership" of the code.