Fix FALLTHROUGH comments.

Stop using the register keyword in ksh(1)

ksh also does some strange things with it, like put it in argument lists.

No functional change intended.

PR bin/53237 ksh: remove register keyword by Nia

Stop using the register keyword in ksh(1)

ksh also does some strange things with it, like put it in argument lists.

No functional change intended.

PR bin/53237 ksh: remove register keyword by Nia Alarie

show more ...

ksh: Rename a local function tsearch to mytsearch

This removes a clash with well-known libc function tsearch(3) from POSIX.

This allows to build ksh against MSan.

The new name might not be perfect

ksh: Rename a local function tsearch to mytsearch

This removes a clash with well-known libc function tsearch(3) from POSIX.

This allows to build ksh against MSan.

The new name might not be perfect, but long term ksh should be switched to
the libc version.

Sponsored by <The NetBSD Foundation>

show more ...

ksh: Upgrade to C99 <stdbool.h>

This shell already used C99 functions.

ksh: Assume ANSI C prototypes

ksh: Use ANSI C varargs, drop support for older version <varargs.h>

Reapply removal of code from 90ties for OS/2 Cygwin AIX HPUX SCOUnix

Added missing #endif terminator in emacs.c

Temporarily revert previous.

emacs.* gets wrong code in generation

Remove os2 support in ksh(1)

OK by <kre>

Don't use non-literal format strings.

The previous commit removed a { } block, and unintendedly introduced a
C99ism (inlined variable declaration), which hurts when pdksh is used
for bootstrapping pkgsrc. Move the two declarations to the

The previous commit removed a { } block, and unintendedly introduced a
C99ism (inlined variable declaration), which hurts when pdksh is used
for bootstrapping pkgsrc. Move the two declarations to the beginning
of the block.

show more ...

In foo="`echo \"hi\"`", the backslashes should be removed by the outer
double quotes, not seen by the inner backquotes. Previously, ksh(1)
handled this correctly in non-posix mode but incorrectly in

In foo="`echo \"hi\"`", the backslashes should be removed by the outer
double quotes, not seen by the inner backquotes. Previously, ksh(1)
handled this correctly in non-posix mode but incorrectly in posix mode.

The previous comments in src/bin/ksh/lex.c quote parts of some version
of the POSIX specification. The version of POSIX being quoted is not
identified, but the wording is very similar to that in SUSv3
<http://www.opengroup.org/onlinepubs/009695399/utilities/xcu_chap02.html>.

It seems clear that the words "having escape characters removed"
mean, in that context, that the backslash before the double quote in
"...`...\"...`..." is removed as part of the handling of the outer
double quotes, so that the backslash is not present when the inner
backquotes are handled. The new code in this commit follows this
interpretation. The previous code followed a different interpretation
which is now believed to be incorrect.

Discussed in tech-userlevel. Closes PR 26493.

show more ...

The following should print \"; from OpenBSD
$ cat << EOF
\"
EOF

Fixed wrong use of the <ctype.h> functions by adding an explicit conversion
to unsigned char. Approved by christos.

Cleanup of ksh memory handling from OpenBSD, via Stefan Krueger in PR 24962.
Should also fix:
PR 8153
PR 13301
PR 15256
PR 25084

Add NetBSD RCS Ids.

The Double-Semi-Colon Police.

make this build with -Werror

resolve conflicts

char->unsigned char casts for is*()

Add some braces to make egcs happy.

Fix compiler warnings
Add WARNS=1

RCS ID Police

import pdksh 5.2.12

import pdksh 5.2.11