Closed GoogleCodeExporter closed 9 years ago
I think that this form of range checking at the XML-reading stage doesn't make
very much sense in the first place. If the values are outside the acceptable
range, that should have been detected and dealt with when the file was written.
I'm inclined to remove the bounds definitions when the file is saved, and in a
later release changing the signature of the addFloatArray function to remove
the minval andm axval arguments.
Original comment by yarmond
on 6 Jun 2012 at 7:02
Thank you for dealing with this issue! I also think that capturing this effect
before the solution file is written is a good idea. Still, I personally would
say that the range check does make sense for the case that someone tempers with
the solution file.
Original comment by thetruet...@googlemail.com
on 18 Jun 2012 at 12:11
Original comment by yarmond
on 21 Jun 2012 at 8:07
This issue was closed by revision r2230.
Original comment by yarmond
on 12 Apr 2013 at 11:07
Original issue reported on code.google.com by
thetruet...@googlemail.com
on 4 Jun 2012 at 12:16