Opened 8 years ago
Closed 8 years ago
#670 closed bug (fixed)
inconsistend behaviour of intvecs if stored as list elements
Reported by: | ren | Owned by: | somebody |
---|---|---|---|
Priority: | minor | Milestone: | 4-1-0 and higher |
Component: | dontKnow | Version: | 4-0-1 |
Keywords: | Cc: |
Description
ren@mandelbrot:~/Sources2/Singular$ ./Singular SINGULAR / Development A Computer Algebra System for Polynomial Computations / version 4.0.1 0< by: W. Decker, G.-M. Greuel, G. Pfister, H. Schoenemann \ Sep 2014 FB Mathematik der Universitaet, D-67653 Kaiserslautern \ // ** executing /home/ren/Sources2/Singular/LIB/.singularrc > intvec v=1,2,3; > v = 0,v; > v; 0,1,2,3 > list L = intvec(1,2,3); > L[1] = 0,L[1]; ? assign not impl. ? error occurred in or before STDIN line 7: `L[1] = 0,L[1];`
Note: See
TracTickets for help on using
tickets.
Not so easy: in the first case v is an intvec, so this is an assignment of a list of (int,intvec) to an intvec. In the second case L[1] is untyped, so is is an assignment of a list (i,iv) to def.
To solve it, use c268ebdb845b116662ce209cd17398864b707404 together with an explicit conversion to intvec:
should now work.