Opened 9 years ago
Closed 9 years ago
#545 closed proposed feature (wontfix)
unfortunate data representation in ringlist[5] and ringlist[6]
| Reported by: | Owned by: | somebody | |
|---|---|---|---|
| Priority: | minor | Milestone: | 4-1-0 and higher |
| Component: | singular-kernel | Version: | 4-0-0 |
| Keywords: | noncommutative relations ringlist | Cc: |
Description
when creating rings with noncommutative relations, in ringlist[5] and ringlist[6] polynomials are stored, which leads to the problem described in
www.singular.uni-kl.de:8002/trac/ticket/542
Proposal:
-store string representations of the noncommutative relations instead of polynomials in ringlist. -When creating a ring, use 'execute'.
Comments/suggestions?
Note: See
TracTickets for help on using
tickets.
ringlist was introduced to overcome the problems with execute - so string representation is a bad idea. For most purposes just keep the internal representation (i.e. equivalent to fetch), All others (i.e. very few) should simply delete L[5] and L[6] and construct the new values (even, if they insists from strings)