close
Warning:
Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
May 14, 2010, 7:04:30 AM (16 years ago)
- Author:
-
Víctor de Buen Remiro
- Comment:
-
I think the wrong behaviour is in v.2.0.1 due you are not modifying Set Ser_. With new OOP features, internal structures and classes are more protected to ensure coherence but in this case you are creating a new object, not modifying it.
You can observe how the set is not modifyied running
Polyn Pol = 0.08+0.05*B;
Set Ser_ = InputDef(Pol, SubSer(Gaussian(100,1, Diario), y2000, y2002));
Set Ser_ << SetOfText("");
Text strName = StructName(Ser_);
Real card = Card(Ser_);
I'm almost sure the problem is a C++ internal copy of a Set that is inheriting the structure inside the operator <<
Legend:
- Unmodified
- Added
- Removed
- Modified
-
-
Property
Status
changed from
new
to
accepted
-
|
initial
|
v1
|
|
| 1 | 1 | There is a strange behavior with versions 1.1.7 and 1.1.7_Bridge that does not happen or has been fixed with version 2. |
| 2 | 2 | If we throw this piece of code on the version 1.7 |
| 3 | | |
| | 3 | {{{ |
| 4 | 4 | Polyn Pol = 0.08+0.05*B; |
| 5 | | Set Ser_ = InputDef(KK, SubSer(Gaussian(100,1, Diario), y2000, y2002)); |
| | 5 | Set Ser_ = InputDef(Pol, SubSer(Gaussian(100,1, Diario), y2000, y2002)); |
| 6 | 6 | Set Ser_ << SetOfText(""); |
| 7 | | |
| | 7 | }}} |
| 8 | 8 | Adding an additional item to a Set with defined structure is not returned as a warning or error. |
| 9 | 9 | |
| 10 | | If we launched it in version 2: |
| 11 | | |
| 12 | | Polyn Pol = 0.08+0.05*B; |
| 13 | | Set Ser_ = @InputDef(KK, SubSer(Gaussian(100,1, Diario), y2000, y2002)); |
| 14 | | Set Ser_ << SetOfText(""); |
| 15 | | |
| 16 | | We have the error when trying to modify a Set by adding an unspecified element in the structure. |
| | 10 | If we launched it in version 2, we have the error when trying to modify a Set by adding an unspecified element in the structure. |
| 17 | 11 | |
| 18 | 12 | How 1.1.7 and 1.1.7_Bridge versions should not warn of this type of behavior? |