Re: Re: Release 2.2 beta#1 of SmartEiffel is available.

Hello,

> Very good. Thanks to the SE team. I would like to know how
> much of REPOSITORY is working.

Unfortunately, none yet. We first implemented the Eiffel parts and the 
tutorial, since it showed us the use cases.

The compiler support currently being written (INTERNALS built_in 
features), but not yet available.

> From the CVS logs on the snapshot page, I gather that STRING and
> perhaps certain heirs of COLLECTION[STRING] can already be stored. Or
> is there more yet?

Only STRING, COLLECTION and other storage-related classes will be marked 
as STORABLE in the standard library. You are usually expected to provided 
your own classes that inherit from STORABLE.

Note that a REPOSITORY can contain only STORABLE, that does not mean that 
nested objects (attributes) are not saved. Beware the double negation: 
attributes *are* stored, obviously, even if they are not themselves 
STORABLE. We are not talking Java ;o) In the same way, COLLECTION is 
STORABLE, so *any* collection is storable; even COLLECTION[INTEGER].

In other words, it means that you are not expected to directly store an 
INTEGER, but a meaningful class. I think it is not a big constraint: any 
OO project has concepts and meaningful classes. Just make those classes 
inherit from STORABLE.

> And are the examples in the tutorial already working?

Not yet. The compiler support is still missing. We hope it will be ready 
before beta2.

Stay tuned ;o)

Best regards,
--
Cyril Adrian -- ALPLOG
@ PSA Peugeot Citroën, Sochaux, France
tél. +33 (0)3 81 33 48 76
fax +33 (0)3 81 33 16 06