Opened 10 years ago
Closed 10 years ago
#486 closed bug (fixed)
Priority of parameters too low
Reported by: | gorzel | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | 3-2-0 and higher |
Component: | singular-kernel | Version: | 3-1-6 |
Keywords: | Cc: |
Description
Every thing is okay here:
> proc tstvar() { ring r0 = 0,(s,x,y),dp; poly g = s*x-y; g; } > tstvar(); sx-y > proc tstpar() { ring r0s = (0,s),(x,y),dp; poly g = s*x-y; g; } > tstpar(); (s)*x-y
Now it comes to a conflict with the parameter s, if another variable with name s is defined on Top level:
> string s; > tstvar(); // still OK sx-y > tstpar(); // fails ? `int` * `string` failed ? expected `int` * `int` ? expected `int` * `matrix` ? expected `int` * `intvec` ? expected `int` * `intmat` ? expected `int` * `bigintmat` ? error occurred in or before ::tstpar line 4: ` poly g = s*x-y;` ? expected poly-expression. type 'help poly;' ? leaving ::tstpar skipping text from `;` error at token `)`
The behaviour is the same, if string s is defined riggt at the beginning.
Note: See
TracTickets for help on using
tickets.
fixed.