no attribute of attributes...

[Oleksandr]

attrib2.tst   4. def s = "ssss";
attrib2.tst   5> attrib(s, "?I?", 2);
attrib2.tst   6> attrib(s);
attr:?I?, type int 

attrib2.tst   9. def a = list(1, "str");
attrib2.tst  10> attrib(a, "?S?", s);
attrib2.tst  11> attrib(a);
attr:?S?, type string 

attrib2.tst  14. def t = attrib(a, "?S?"); t; t == s;
ssss
1

attrib2.tst  17. attrib(t); // BUG: no "?I?" attribute!!!!!!!!!!!!!!!!!!!!
no attributes

[Oleksandr]

attrib of attrib???

[hannes]

Do we really want to attributes of attributes ? According to the documentation, only expressions can have attribute while attributes are a set of tripels: (key, type,value).

[Oleksandr]

Is it unnatural to expect EXACTLY THE SAME value to be stored as an attribute? i.e. in the above example: t doesn't have the same attributes as s and therefore t != s, that is, some important information was quietly lost...

[Oleksandr]

We tried the following in muiltigrading.lib:

1. multi-graded ring has several attributes: variable weights and grading group

2. groups themselves are useful structures and have their own attributes

of course one can transfer those group-related attributes to the corresponding ring but it is plain wrong and UGLY.

[hannes]

It is not a bug - the implementation is according to the definition/description. If we reaaly want this, it would be something new.