GIMP Procedural Database and Script‑Fu: Interoperability When Procedures Are Deprecated

Goal: Determine whether GIMP’s Procedural Database can provide transparent rollback safety for Script‑Fu when a procedure’s signature changes or is deprecated, so that existing scripts do not need immediate modification.

Constraints: The PDB currently keeps a deprecated flag but does not redirect calls; missing procedures raise errors that script authors must handle. Introducing a compatibility shim could automate rollback, yet its runtime cost and UI exposure remain unresolved.

Questions: Should the PDB automatically invoke a shim for deprecated calls? What performance impact would such a shim have on typical script execution? How could GIMP expose versioning or compatibility information to script authors without cluttering the interface?