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

Compatibility and the Procedural Database

The GIMP Procedural Database (PDB) cannot currently provide transparent rollback safety for Script-Fu. Because the PDB acts as a direct registry for C-based procedures, it lacks a native redirection or aliasing layer. When a procedure is deprecated or its signature changes, the PDB does not automatically map the old call to a new version; it simply fails to find the requested procedure or rejects the argument count, triggering a runtime error in the script.

Feasibility of an Automated Shim

Implementing a compatibility shim is technically feasible but involves a trade-off between stability and maintenance. To achieve this, an interceptor layer would need to be inserted into the PDB dispatch logic. This layer would catch calls to deprecated procedures and translate the arguments to match the current API signature before forwarding the request.

Performance Impact: For typical Script-Fu execution, the performance overhead of such a shim would be negligible. The primary bottleneck in GIMP scripts is almost always the image processing task (pixel manipulation, filter application) rather than the PDB lookup or argument translation process.

Proposed Implementation Strategy

To introduce this functionality without cluttering the UI or compromising core stability, the following approach is recommended:

• Metadata-Driven Redirection: Utilize the existing PDB metadata fields to store a "replacement" procedure ID. The dispatcher can check this field when a procedure is flagged as deprecated.
• Programmatic Versioning: Instead of adding UI elements, allow scripts to query the PDB for procedure status. Script authors can use a wrapper function to check if a procedure is deprecated and handle the transition gracefully.
• Strict Opt-in: To avoid silent failures where a new procedure behaves differently than the old one, shims should be limited to cases where the behavior is functionally identical despite the signature change.

Verification Steps

To confirm current behavior and test potential shim logic, use the following methods:

1. PDB Browser: Navigate to Filters > Procedural Database to inspect the registered signatures of the procedures you intend to shim.
2. Console Testing: Execute a known deprecated call in the Script-Fu console. Confirm that it currently produces an error rather than a redirected result.
3. Source Audit: Review the PDB registration and dispatch modules in the GIMP C source to identify the exact hook point for the interceptor layer.

Missing Diagnostic: To refine this recommendation, it is necessary to know if the deprecations in question involve simple argument reordering or fundamental changes in the underlying C-function logic, as the latter makes automated shimming unsafe.