Summary: | Inconsistent use of signalerror | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | Peter Cherepanov <sphinx.pinastri> |
Component: | PS Interpreter | Assignee: | Ray Johnston <ray.johnston> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | P4 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
Customer: | Word Size: | --- | |
Attachments: |
Patch
New patch |
Fixed in commit 00f554cfaf1f973edf0404a3a0bfe64a1c63f631 Thanks, Peter. |
Created attachment 20330 [details] Patch The first operand of signalerror should be executable to appear without a leading slash in the error message. The execution status of the second operand is inconsequential. This patch brings all relevant calls to signalerror to the following pattern: /NAME cvx /ERROR signalerror The patch also corrects one real bug, that would look up an undefined name. } { - /readorigxref cvx /rangecheckerror signalerror + /readorigxref cvx /rangecheck signalerror } ifelse