[pstricks] strange conflict (?)

Michael Sharpe msharpe at ucsd.edu
Wed Nov 12 01:29:53 CET 2008


In fact, it's enough to change x and y in the \pstVerb code to xx and  
yy, and make the corresponding changes elsewhere.

Michael

On Nov 11, 2008, at 11:44 AM, Zbigniew Nitecki wrote:

> The following pspicture prints fine when it is the complete text of  
> a short test file, but when run in the context of a larger file, it  
> yields no error messages while texing, but then yields the error  
> which follows the *****
>
> *****************************************************************************************************
> \begin{figure}[htbp]
> \begin{center}
> 	\begin{pspicture}(-2,-2)(2,2)
> 		\psline{<->}(-1.5,0)(1.5,0)
> 		\psline{<->}(0,-1.5)(0,1.5)
> 		\multido{\rx=-1+0.25}{9}{%
> 				\multido{\ry=-1+0.25}{9}{%
> 					\pstVerb{
> 					/x \rx\space def
> 					/y \ry\space def
> 					/ValueTempA \ry\space 2 div def
> 					/ValueTempB \rx\space 2 div def
> 					}
> 					\psset{arrows=->}
> 					\psline(!x y)(!x ValueTempA add y ValueTempB add)
> 				}
> 		}
> 	\end{pspicture}
> %\caption{The vector field $\vFof{x,y}=y\vi+x\vj$}
> \label{fig: vfieldyx}
> \end{center}
> \end{figure}%
> ***************************************************************************************************
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
> +++
> Error: /invalidrestore in --restore--
> Operand stack:
>    (\feld)   1751   4702   1.0   (!)   1761   4764   1.0   (y)    
> 2222   4725   1.0   (!)   2252   4764   1.0   (x)   2476   4725    
> 1.0   (!)   2504   4764   1.0   (|)   664   4959   1.0   -- 
> nostringval--   --nostringval--
> Execution stack:
>    %interp_exit   .runexec2   --nostringval--   --nostringval--   -- 
> nostringval--   2   %stopped_push   --nostringval--   -- 
> nostringval--   --nostringval--   false   1   %stopped_push   1905    
> 1   3   %oparray_pop   1904   1   3   %oparray_pop   1888   1   3    
> %oparray_pop   1771   1   3   %oparray_pop   --nostringval--    
> %errorexec_pop   .runexec2   --nostringval--   --nostringval--   -- 
> nostringval--   2   %stopped_push   --nostringval--   -- 
> nostringval--   1834   29   4   %oparray_pop   --nostringval--    
> 1818   29   4   %oparray_pop   --nostringval--
> Dictionary stack:
>    --dict:1148/1684(ro)(G)--   --dict:0/20(G)--   --dict: 
> 115/200(L)--   --dict:227/300(L)--
> Current allocation mode is local
> Last OS error: 2
> Current file position is 8962800
> GPL Ghostscript 8.62: Unrecoverable error, exit code 1
> ### FAILED to generate /tmp/altpdflatex.9589-1226431794/ 
> Hardcore2.pdf ()
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 
> +++
> Both the test file and the main text file call the following  
> packages for pstricks (the main text calls others that have nothing  
> to do with pstricks):
>
> \usepackage{amsmath, amssymb}
> \usepackage{pstricks, pst-plot, pst-math, pst-3dplot}
> \usepackage{pst-grad, pst-func, pst-text}
> \usepackage[monochrome]{pstcol}
>
>
> I don't know if the following is a clue to what is going on:  if the  
> caption is uncommented, where
> the relevant macro definitions are
>
> \newcommand{\vFof}[1]{\veof{F}{#1}}
> \newcommand{\veof}[2]{\of{\ve{#1}}{#2}}%vector function
> \newcommand{\of}[2]{\ensuremath{#1\!\left(#2\right)}}%function of
> \newcommand{\ve}[1]{\ensuremath{\overrightarrow{#1}}}
>
> \newcommand{\vi}{\ve{\imath}}
> \newcommand{\vj}{\ve{\jmath}}
>
> then I get the error message
>
> ******************************************************************
> ! Illegal parameter number in definition of \reserved at a.
> <to be read again>
>                    \crcr
> l.45 ...n{The vector field $\vFof{x,y}=y\vi+x\vj$}
> *********************************************************************
>
> Any idea what might be going on?
>
>
>
>
> Zbigniew Nitecki
> Department of Mathematics
> Tufts University
> Medford, MA 02155
>
> telephones:
> Office    (617)627-3843
> Dept.    (617)627-3234
> Dept. fax    (617)627-3966
> http://www.tufts.edu/~znitecki/
>
> _______________________________________________
> PSTricks mailing list
> PSTricks at tug.org
> http://tug.org/mailman/listinfo/pstricks



More information about the PSTricks mailing list