NCX: ArrayMax, ArrayMin: unexpected values

[HaWe]

why not take
1.31
1.3101
1.3102
1.3103
1.3104

[linusa]

I will probably someday increment the firmware version number. Please forgive me for not wanting to completely deviate from the version number of the standard firmware from which the enhanced firmware was created.

From my experience with our mindstorms software and hundreds of students, as well as other software projects: Never have two different releases or versions of your software with the same version number / identifier. Things can get really ugly. If you don't want to change the major version number or the identifier string, that's ok. But you GOT to have some sort of unique identifier in software products, period! You can use a build-number, the SVN-Revision, or a date. But it must be something unique for each version (as in FW image / zip file) that you create. That's just good craftmanship. My cents

[HaWe]

A miracle!
A wonder!
That's probably sort of space-time-singularity:

Linus and me, we have the same opinion...

surely this space-time bubble soon will burst and will dissolve into a logical cloud....(or a worm hole...) (or a new Universe is born...)

[nxtreme]

What Mr. Hansen here really needs to invest in is a box full of USB drives; it's a great way of keeping track of different versions of software!



RTZ