Version of EiffelBase2 shipped with different EiffelStudio versions

[Colin Adams]

I can see from the iron repository that all of 15.01,15.08 and 15.11 have base2. But can I easily tell if they all come with the same version or not (and which version that is)? Iron shows different sha1s, but I don't know if that implies they are different versions.

[javier hector]

I think they are different, EiffelBase2, is a fully verified library  https://svn.eiffel.com/eiffelstudio/trunk/Src/unstable/library/base2/

Check this https://github.com/nadia-polikarpova/eiffelbase2, to play with the online verification. (not sure if it's up to date).

/Javier

[Colin Adams]

I know what EiffelBase2 is. I was asking about the version in the iron repository for each version of EiffelStudio.

--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Colin Adams]

Come on - someone must know - the person who loaded it to iron, e.g.

[Jocelyn Fiat]

Hi all,

Usually the version uploaded to iron server comes from the associated branch

for instance

- 15.01 has almost same content as https://svn.eiffel.com/eiffelstudio/branches/Eiffel_15.01/

- ...

I said "almost" because, the ecf are modified to use iron references rather than $ISE_LIBRARY/... locations.

About versions and Iron package, for now, this is really basic version system .. i.e per major EiffelStudio releases.

Now, I agree that we (the community) should design proper solution to support version per package.

In fact, it would also possible to update, for instance, EiffelBase2 package for previous releases, same for any package, to include new routines, new corrections, and so on.

But version are required for that.

For now internally there is a pseudo notion of "revision", and we need to turn that into a tag/version system.

Colin, as you know, I am working again on Iron service, but not yet full time due to other priorities.

I welcome any comments, suggestions, and collaboration on it.

And I hope to make this project more active very soon.

-- Jocelyn

--

Jocelyn
------------------------------------------------------------------------
Eiffel Software
805-685-1006
http://www.eiffel.com
Customer support: http://support.eiffel.com
User group: http://groups.eiffel.com/join
------------------------------------------------------------------------

[Colin Adams]

But this doesn't answer my question.

Which version of EiffelBase2 ships with which version of EiffelStudio?

[Jocelyn Fiat]

As the author of EiffelBase2 does not define any specific versions, I would say

- EiffelStudio 14.05 ships EiffelBase2 version 14.05, and associated source code can be found at https://svn.eiffel.com/eiffelstudio/branches/Eiffel_14.05/Src/unstable/library/base2/  (last changed revision: 94979)

- EiffelStudio 15.08 ships EiffelBase2 version 15.08, and associated source code can be found at https://svn.eiffel.com/eiffelstudio/branches/Eiffel_15.08/Src/unstable/library/base2/  (last changed revision: 96329)

And diff between them

svn diff https://svn.eiffel.com/eiffelstudio/branches/Eiffel_14.05/Src/unstable/library/base2/ https://svn.eiffel.com/eiffelstudio/branches/Eiffel_15.08/Src/unstable/library/base2/

I am not sure this answer is better than previous.

Maybe Eiffel library authors should maintain a proper version system for each library or iron package.

We could use the package.iron file for this purpose.

Maybe my personal conclusion is what you were expecting .. not an exact answer, but more the acknowledgement that Eiffel libraries usually lacks good standalone versioning (apart from the version coming from EiffelStudio releases).

-- Jocelyn

[Colin Adams]

Not really.

What I need to know is when I run tests on the performance and suitability for use of EiffelBase2, do I have to repeat them with all of ES versions 15.01, 15.08 and 15.11?

[Emmanuel Stapf]

In this particular case, it is sufficient to take any version of EiffelStudio and the EiffelBase2 version that comes with it to evaluate EiffelBase2 as the library has not really changed much in the past few years.

 

In the general case, you should stick to one version of EiffelStudio and compare the different version of the libraries assuming they all compile with the version of EiffelStudio being used.

 

Manu