From fa6cd2132d7e8e3e3dc5e817618c91052c7cb85e Mon Sep 17 00:00:00 2001 From: Sean Whitton Date: Sun, 26 Sep 2021 14:53:19 -0700 Subject: discuss limitations which apply to dumping images with IMAGE-DUMPED Signed-off-by: Sean Whitton --- src/image.lisp | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'src/image.lisp') diff --git a/src/image.lisp b/src/image.lisp index 28e1df1..0f136d5 100644 --- a/src/image.lisp +++ b/src/image.lisp @@ -287,7 +287,8 @@ then quietly skip over this property by applying it like this: ;; a remote Lisp image and every time we establish a further FORK-CONNECTION, ;; however, though perhaps we could arrange to avoid dumping an executable if ;; we know that we aren't going to need to reinvoke it, by having connection -;; types push hostattrs. +;; types push hostattrs. We would also need to resolve issues detailed under +;; "Dumping and reinvoking Lisp" in pitfalls.rst. ;; ;; If we took this approach, then we'd have implementation-specific dumping ;; code, but the code to reinvoke the dumped images would be fully portable -- -- cgit v1.2.3