Red Hat Bugzilla – Bug 483502
asymptote gets ambiguous function calls from pstoedit
Last modified: 2009-02-18 13:48:03 EST
Description of problem:
As a results of experiments with a facility described in "PostScript to Asymptote" chapter of asymptote manual, and using venn.eps example as described there, I was getting an asymptote code which, when fed back to asymptote, generated complaints like that:
test.asy: 27.10: call of function 'beginclip(guide)' is ambiguous
Only after appending ', false, currentpen, true' to call arguments to get a signature of a function defined in runtime.cc from asymptote sources that code was accepted without any complaints. (BTW - the second pair of beginclip .. endclip is not really needed in that example).
A simpler way out appear to be to comment out beginclip and endclip definitions in /usr/share/asymptote/pstoedit.asy. With that everything worked as expected when I tried without any changes in a pstoedit generated code. Just dropping the whole 'import pstoedit;' is not an option as this causes "cannot call 'void gsave(frame f)' without parameters" complaints.
Version-Release number of selected component (if applicable):
as described above
It did not matter if I patched or not pstoedit following "PostScript to Asymptote" chapter of asymptote manual. Actually results looked the same before and after but maybe differences will show up in some other examples?
This is fixed in 1.63-4 (in rawhide).