🚀 go-pugleaf

In reply to my original question about PATCH & similar things,
several people discussed this theme *only* in the view of a
software producer who might (or should not) distribute patches
instead of new images.

Is there no-one who shares my view as an end-user that the ability to
PATCH a distributed program has some value? I've come across a few
situations where I could rather easily "patch in" some feature
considered necessary at our site, but either there was no way
to convince the producer (e.g. DEC) that our problem was warranting
a change to their product, or their timescale was just *very* different
from ours (like many problems "submitted to VMS engineering").

Sure, patching data, or NOPping instructions does not absolutely
require a tool like MACRO32-level PATCH, but I'd rather not miss
*some* of its features (in particular the ability to extend
a program section).

Wolfgang J. Moeller, GWDG, D-3400 Goettingen, F.R.Germany | Disclaimer ...
PSI%(0262)45050352008::MOELLER      Phone: +49 551 201516 | No claim intended!
Internet: moeller@gwdgv1.dnet.gwdg.de   | This space intentionally left blank.