[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#490605: [...] assumes printf is a builtin



-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Steve Langasek dixit:

>Have you looked at this set yet, by chance,
>to see if there are others besides printf that mksh doesn't share with dash

Here they are:

Builtins in mksh (-current from CVS), but not in dash (source from sid):
* bind (interactive)
* builtin
* fc (interactive)
* let (fancy for (( ... )) )
* mknod (another speed hack, OpenBSD's responsible for this one)
* print (Korn shell command)
* realpath (same as "readlink -f" from base)
* rename (similar to mv but doesn't copy; sometimes a life-saver)
* typeset (Korn shell command)
* whence (Korn shell command; whence -p approximately equals which)

Builtins in dash, but not in mksh:

* chdir (use cd instead)
* printf

dash builtins implemented as built-in macros in mksh:

* hash (alias -t)
* local (typeset)
* type (whence -v, but it's the same as command -V in dash+mksh)

The macro versions do not pose a threat because the macros are
"always" defined. (We had versions that didn't define them, ex-
cept local, for a /bin/sh, but these are long gone.)

So, the only mismatches are chdir (which could arguably be added
as a Debian-local patch, unless shows me the benefit of having it
upstream as well - if desired at all, that is; what does bash do?)
and printf (the topic of this discussion).

>and bash?

Having looked at dash, I think I don't need to, since the team
which converted /bin/sh to dash should already have done so ;-)

bye,
//mirabilos
- -- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
	-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MirBSD)

iQIVAwUBSnCN1Xa1NLLpkAfgAQOEPg//Wuj9yQbbDkiooDAObflE6hJzG/bpGvQF
ZNdCUX6p9wlvmpyIzXzOPf3+Q2XGyq8PaQ4O4ByX8J/oMrYG77M5NxzMh3L4DR/t
+a9DB90KS4YRRt1heQviJgHR+lxeYZLf9X/wlRSVaQ2x3cKeuO7KBCk3Hjkwir2e
Girza5gvtn+Za7ffvjGSHRYWQEcT28g1E/iyi9kwMLgw3A4REIRFouwF8ME1+wdT
jpF2nSqye1Y6G/5pZBrUjGsUNuOIfvoBK04s22K3y6vjwP8X2oM+OOte7H5/z3h9
xvvEJZx/BsCS9BmnOJd6OM2tK4eaA+2+NXdg45aMDNLuGZ5sq/XVoK36DgjF0PlM
0+Q81rZD7ulV6Gg72/Flty5bsv1ZrG+JpsUTv7dcOKmeyO7oJM0wFwkePqNkBNka
DmSgV4tIjscHxzZMUzldbkEDCUQBIH91ePf0q/SiWPLcPGnX83K1O5sarfIy5c52
UIckccUgIq2nYbVkxMTHV2YwNj8/oFTadoDTB8Z3E3/sLHFindBjcQuDOv+/YlNt
VISDa622whq6VQhs2CPU2K0+JLFjbpXd/16gTgBYTPCAPKXQA9vOFlPuVDF6Zmj7
aSzmTa0RwCOCsPXzOiVmZRNllJIri5tDvq1hqtvOPlH8acMQfgi3a49GVdAvx1ek
V1XmcXcQZ6k=
=2s5t
-----END PGP SIGNATURE-----



Reply to: