[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Feature request - make type show that a builtin is a loadable
From: |
Geir Hauge |
Subject: |
Feature request - make type show that a builtin is a loadable |
Date: |
Sun, 23 Oct 2022 21:39:21 +0200 |
I think it's a good idea for the type builtin to distinguish between
static and loadable builtins, and for debugging scripts that use
loadable builtins, it would be useful to be able to see which file got
loaded. For example in cases where BASH_LOADABLES_PATH was
unintentionally unset or set to a wrong path.
I had a go at implementing it and cobbled together the attached patch.
It extends struct builtin with a new path field that gets set to the
path that was passed to dlopen. The type builtin then includes that path
in its output if it is set.
$ ./bash -c 'enable csv; type [ csv'
[ is a shell builtin
csv is a shell builtin (/usr/local/lib/bash/csv)
$ BASH_LOADABLES_PATH=$PWD/examples/loadables ./bash -c 'enable csv; type [
csv'
[ is a shell builtin
csv is a shell builtin (/Users/geirha/bash/examples/loadables/csv)
Continuing on the debugging aspect, I think it would also be useful if
enable would warn or fail if you try to enable a loadable builtin that
was built against a different bash version. The easiest is probably to
embed the bash version inside the loadable file somehow, and compare
that when loading. Giving something like:
$ enable csv
bash: enable: /usr/local/lib/bash/csv: builtin was built for bash-5.1.16
Not sure how to go about implementing that though, or if it's even a
good approach. After all, you could potentially have multiple bash
builds of the same version with different configure options, which could
potentially leave out some function the loadable builtin expects to use.
--
Geir Hauge
include-loadables-path.patch
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Feature request - make type show that a builtin is a loadable,
Geir Hauge <=