Now christophe went on vacation.
On 23/7/14 14:24, Sven Van Caekenberghe wrote:
On 23 Jul 2014, at 14:13, stepharo wrote:
Now we should probably not haeve an explicit reference to the dependency class
In STON it is possible to use an 'external name' for a class, see #stonName and
#lookupCla
On 23 Jul 2014, at 14:13, stepharo wrote:
> Now we should probably not haeve an explicit reference to the dependency class
In STON it is possible to use an 'external name' for a class, see #stonName and
#lookupClass: - that way there is no explicit dependency on a concrete class.
Some explicit examples would probably help.
On 23 Jul 2014, at 14:13, stepharo wrote:
> I do not have the exact points that christophe wants. Now he wants to store
> package dependencies into package manifest.
> And I told him to use STON. Now we should probably not haeve an explicit
> referen
I do not have the exact points that christophe wants. Now he wants to
store package dependencies into package manifest.
And I told him to use STON. Now we should probably not haeve an explicit
reference to the dependency class
Stef
Hi Christophe,
Sorry for the delay, I was on holiday.
On 15
Hi Christophe,
Sorry for the delay, I was on holiday.
On 15 Jul 2014, at 14:46, Christophe Demarey
wrote:
> Hi,
>
> I read the STON paper and the STON chapter in EnterprisePharo but I did not
> find answers to some questions:
> • how do you tell STON to not serialize some variables of
Hi,
I read the STON paper and the STON chapter in EnterprisePharo but I did not
find answers to some questions:
how do you tell STON to not serialize some variables of an object?
is there a way to avoid the class tag? What I mean is that I would like a
synthetic STON String. If a STON entry has