Bug 703237 - Inconsistent use of signalerror
Summary: Inconsistent use of signalerror
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PS Interpreter (show other bugs)
Version: master
Hardware: PC Linux
: P4 normal
Assignee: Ray Johnston
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-07 21:26 UTC by Peter Cherepanov
Modified: 2021-05-04 17:34 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
Patch (11.65 KB, patch)
2020-12-07 21:26 UTC, Peter Cherepanov 		Details | Diff
New patch (10.26 KB, patch)
2020-12-10 07:37 UTC, Peter Cherepanov 		Details | Diff
Show Obsolete (1) Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Cherepanov 2020-12-07 21:26:19 UTC 
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
Comment 2 Ray Johnston 2021-05-04 17:34:27 UTC 
Fixed in commit 00f554cfaf1f973edf0404a3a0bfe64a1c63f631

Thanks, Peter.