Also, as has been already mentioned, the year version may or may not imply an
actual major version (i.e., changes that imply an important or significant API
change, which not necessarily means backward incompatibility) so to find out it
will be necessary to dive into the change log. The only
Am 22.02.23 um 10:44 schrieb DAVID Clément:
Hello Wolfgang,
Which Scilab version do you prefer?
Samuel
for checking. There are a lot of zcos files created with 5.5.2, and it would be
helpful to be able to open and work on them with 6.0
Could you point me or comment on GitLab what zcos
Dear Alain,
Thanks for your message.
For Scilab users, incompatibility mainly comes from functions renaming, removal
or incompatible prototype change. In the past, this kind of change could even
occur in patch versions (which could be released more than once a year).
With this new release
Dear Scilab users / team,
Just one opinion among others:
That's nice to have new Scilab releases regularly, provided of course that
backward compatibility is guaranteed us much as possible, except maybe for
major versions.
But I don't see the need for changing the versioning convention.
For
Hello Wolfgang,
> > Which Scilab version do you prefer?
> >
> > Samuel
>
> for checking. There are a lot of zcos files created with 5.5.2, and it would
> be
> helpful to be able to open and work on them with 6.0
Could you point me or comment on GitLab what zcos file, produced with 5.5.2,
Am 21.02.23 um 21:40 schrieb Samuel Gougeon:
Le 20/02/2023 à 19:41, Wolfgang Engelmann a écrit :
Am 20.02.23 um 19:31 schrieb Wolfgang Engelmann:
.../...
ps *** not in the left upper part, but at the right. The text "gain 1"
was below the clock symbol which contains "text" instead of "gain
