forked from ksh-community/ksh
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "[v1.0] Remove experimental .getn discipline"
This reverts commit 42fc5c4. It somehow caused the following reproducer to fail. Reason unknown. typeset -i x function x.set { :; } x[0]=0 unset x typeset -p x Expected output: none Actual output: typeset -a -i x=() The 'x' variable fails to be unset. With the .get and .getn discipline functions instead of .set, the above reproducer still fails even after the revert, but that always has failed, back to at least 93u+ 2012-08-01. This is yet more evidence that discipline functions are a mess. But a proper cleanup will require a lot of time and very thorough testing, so it will have to wait until some future release. src/cmd/ksh93/tests/variables.sh: - In addition to the revert, add the above reproducer as a regression test for the .set, .unset and .append disciplines.
- Loading branch information
Showing
4 changed files
with
73 additions
and
16 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