-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
cleanup: complete the transition from stak(3) to stk(3)/sfio(3)
Having two different interfaces to the same AST stack routines is a botch that damages code legibility. The "new" stk(3) interface is a reimplementation (on top of sfio(3)) of the old stak(3) routines, the latter now being just a set of macros that use the former. The code liberally mixes both interfcaces. I'm scare-quoted "new" above because, as the ksh93-history repo shows, the new stk(3) interface has been present since 1995 or before! I am not aware of any surviving copy of the original stak(3) routines. Yet, the transition was never close to completed, not even in the last AT&T beta from 2016. This commit finally finishes the job. Unless I've done something wrong, there should be no change in ksh's behaviour. src/lib/libast/include/stak.h, src/lib/libast/man/stak.3: - Removed. Every other file: - Translate the ancient interface to the slightly less ancient one. - Related housekeeping.
- Loading branch information
Showing
54 changed files
with
694 additions
and
1,029 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.