Am 05.11.2018 um 03:53 teilte Norbert Preining mit:
Hi all,
No, I don't think so. As mentioned in the link you sent, the correct way
would be to say
asy -nosafe ...
Just my IMHO.
Dimitry, can you check whether adding the -nosafe option to asy helps
you?
I tend to close this bug report.
I can confirm that the workaround (using -nosafe) does solve the problem.
Nevertheless I tend to see it as bug if asy generates input files, which
needs a special mode in gs to be processed successfully. Either asy
should call gs w/ -nosafe by default (not!) or it should generate
generic code, which can be processed w/ option -nosafe.
Hilmar
--
#206401 http://counter.li.org
