dump-image is always dumping an image on all implementations. On *some* implementations, these images happen to also always be executable, even though they don't count as "self-contained, end-user-ready executables" (but :self-contained-end-user-ready-executable might have been a bit much instead of :executable).
I'm not opposed to adding a flag :image-only or something to allow programmers to specify they don't want it executable, but then please do it right and maintain backward compatibility.
—♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org A true intellectual is a man who, after reading a book and being convinced by its arguments, will shoot someone or, more likely, order someone shot. — John McCarthy
On Thu, Dec 3, 2020 at 3:12 AM Pierre Neidhardt mail@ambrevar.xyz wrote:
Thank you!
I believe both Fahree and Eric are making fare points.
If executables it's going to be, then I suggest the following:
Update the docstring to explain that executables are always generated, and why.
Optional: Supersede `dump-image` with a new `dump-executable` which would be less misleading :)
Cheers!
-- Pierre Neidhardt https://ambrevar.xyz/