#pdksh — Public Fediverse posts

#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C library licence the Sun CDDL would likely be a problem.

https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs/heads/master/usr/src/lib/libc/port/regex/wordexp.c

So if one is looking for "easily", where one just imports a compatibly-licenced and #KornShell-compatible existing implementation, the answer seems to be "No.".

#pdksh

#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C library licence the Sun CDDL would likely be a problem.

https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs/heads/master/usr/src/lib/libc/port/regex/wordexp.c

So if one is looking for "easily", where one just imports a compatibly-licenced and #KornShell-compatible existing implementation, the answer seems to be "No.".

#pdksh

#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C library licence the Sun CDDL would likely be a problem.

https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs/heads/master/usr/src/lib/libc/port/regex/wordexp.c

So if one is looking for "easily", where one just imports a compatibly-licenced and #KornShell-compatible existing implementation, the answer seems to be "No.".

#pdksh

#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C library licence the Sun CDDL would likely be a problem.

https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs/heads/master/usr/src/lib/libc/port/regex/wordexp.c

So if one is looking for "easily", where one just imports a compatibly-licenced and #KornShell-compatible existing implementation, the answer seems to be "No.".

#pdksh

#Illumos has another #wordexp implementation (originating with Mortice-Kern, no less!) that expects a Korn (93) shell and uses its printf (and set -o), which might be tweakable to function with #OpenBSD's PD Korn shell; but like the GNU C library licence the Sun CDDL would likely be a problem.

https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs/heads/master/usr/src/lib/libc/port/regex/wordexp.c

So if one is looking for "easily", where one just imports a compatibly-licenced and #KornShell-compatible existing implementation, the answer seems to be "No.".

#pdksh

#Poll: Curious about people's attitudes towards shell scripting.

Two part question:

1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

#Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

#Poll: Curious about people's attitudes towards shell scripting.

Two part question:

1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

#Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

#Poll: Curious about people's attitudes towards shell scripting.

Two part question:

1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

#Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

#Poll: Curious about people's attitudes towards shell scripting.

Two part question:

1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

#Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

#Poll: Curious about people's attitudes towards shell scripting.

Two part question:

1. Are you a DEVeloper (or working in a development-heavy role), OTHER-IT worker (such as a sysadmin, architect, anything in a non-development-heavy role), or NON-IT (accountant, doctor, whatever)
2. Do you HATE shell scripting, are you INDIFferent towards (or ignorant of) shell scripting, or do you LOVE it?

#Unix #UnixShell #ShellScript #ShellScripting #POSIX #PosixShell #sh #bash #zsh #csh #tcsh #ksh #pdksh #oksh #mksh

#Shell Ancestry

https://egopontem.com/blog/shell-ancestry
#ksh #csh #bash #tcsh #pdksh #etceterash

#Shell Ancestry

https://egopontem.com/blog/shell-ancestry
#ksh #csh #bash #tcsh #pdksh #etceterash

#Shell Ancestry

https://egopontem.com/blog/shell-ancestry
#ksh #csh #bash #tcsh #pdksh #etceterash

@pixelherodev
I mean, it really depends. It's mostly an academic exercise.

I have at&t ksh installed on my linux daily driver, I know it's 2-4x faster than bash, but all of my scripts are still in bash (even the ones that would be trivial to convert).

20 years ago, the difference mattered a lot more to me than it does now.

I guess I'm still just wondering why #OpenBSD still uses pdksh (and why #pdksh is still a thing). Probably just history. Already audited, don't mess with it.

Just as I suspected, the raw loop speed on at&t #ksh is a lot faster than #pdksh, even on #OpenBSD.

Not sure if that really matters, but I've always known "true" ksh to be a decent bit faster than bash or pdksh, for reasons unknown to me.