[ANN] Magma 1.1r2

I am pleased to announce a new release of Magma containing my updates
since 1.1r1:

- All underscore assignments have now been updated to ANSI assignments.
- When opening the server, a file called "_open" is created in the
repository directory, to indicate the repository is open.  The file is
deleted when the repository is closed gracefully.  This is intended to
help protect from accidentally letting two OS processes open the same
repository files.
- Resurrected MagmaDictionary!  It is just like a Dictionary except
that it inherits the properties of Magma's LargeCollections, such as
size and concurrency.
- Added Collection>>#asMagmaArray and MagmaArray>>#add:.
- Added check for an additional way to run Squeak in headless mode:
the "-vm-display-null" option.
- Added MagmaSessionRequest class>>#signalNewReadStrategy: so that
domains may signal new ReadStrategies to any listening sessions.
- Added MagmaLocalLocation>>#findSession, a convenient counterpart to
#newSession that first checks there is already a session open on that
location and, if so, use that one.  Otherwise, create and answer a new
one.
- Support for persistent, simple BlockClosures (e.g., with only
references to arguments, not "self", any instVars or globals).
- Choose automatically between an appropriate MaDictionary subclass,
depending on whether the new Weak-Finalization mechanism from Igor is
supported.
- Several other minor fixes.

The following represent the 1.1r2 configuration, in load-dependent order:

"Magma client"
{ 'Collections-BTree-lr.73.mcz'.
  'Ma exception handling-cmm.36.mcz'.
  'Ma base additions-cmm.174.mcz'.
  'MaFixedWidthReport-cmm.7.mcz'.
  'Ma Statistics-cmm.24.mcz'.
  'Ma files additions-cmm.13.mcz'.
  'Ma contextual search-cmm.34.mcz'.
  'Ma special collections-cmm.114.mcz'.
  'WriteBarrier-cmm.28.mcz'.
  'Ma Squeak domain-cmm.34.mcz'.
  'Ma proxy support-cmm.42.mcz'.
  'Ma traverse object graphs-cmm.31.mcz'.
  'Ma object serialization-cmm.234.mcz'.
  'Ma client server-cmm.215.mcz'.
  'Magma client-cmm.490.mcz' }

"for Magma server add"
, {'Magma server-cmm.406.mcz'. }

"for Magma tester add"
, { 'Ma Armored Code-cmm.148.mcz'.
  'Ma special collections tester-cmm.14.mcz'.
  'Ma object serialization tester-cmm.32.mcz'.
  'Magma tester-cmm.367.mcz' }

These package versions are available in the "MagmaTester" project of
squeaksource.com.

 - Chris

El jue, 29-07-2010 a las 18:55 -0500, Chris Muller escribió:
> I am pleased to announce a new release of Magma containing my updates
> since 1.1r1:

- All underscore assignments have now been updated to ANSI assignments.

Very Good!

>   'Ma files additions-cmm.13.mcz'.

This is a new package. What other package depends on it?

>
> These package versions are available in the "MagmaTester" project of
> squeaksource.com.
>

Why on MagmaTester? I thought that for released versions, they were
always on Magma repository and that MagmaTester was for your beta and
not released yet versions, isn't that true anymore?

In repository squeaksource.com/WriteBarrier, there are packages:

WriteBarrier-tbn.28.mcz
WriteBarrier-cmm.27.mcz

Then in MagmaTester repository there is

WriteBarrier-cmm.28.mcz

and in Magma there is


--
Miguel Cobá
http://miguel.leugim.com.mx

Premature send

El jue, 29-07-2010 a las 18:55 -0500, Chris Muller escribió:
> I am pleased to announce a new release of Magma containing my updates
> since 1.1r1:

- All underscore assignments have now been updated to ANSI assignments.

Very Good!

>   'Ma files additions-cmm.13.mcz'.

This is a new package. What other package depends on it?

>
> These package versions are available in the "MagmaTester" project of
> squeaksource.com.
>

Why on MagmaTester? I thought that for released versions, they were
always on Magma repository and that MagmaTester was for your beta and
not released yet versions, isn't that true anymore?

In repository squeaksource.com/WriteBarrier, there are packages:

WriteBarrier-tbn.28.mcz
WriteBarrier-cmm.27.mcz

Then in MagmaTester repository there is

WriteBarrier-cmm.28.mcz

and in Magma there is

WriteBarrier-pmm.26.mcz

So I don't understand either, what is the policy here. Is the package
modified, and pushed to the original repo (WriteBarrier) and *then*
copied to MagmaTester and Magma or

Is the package modified in your MagmaTester repo and when finished,
copied to original repo (WriteBarrier) and releases repo (Magma)


I have prepared an update to the configuration of Magma for 1.1r2 with
the preferences corrected but I would like to have all the packages in
WriteBarrier and in Magma (that I consider the releases repositories, or
at least, everything on Magma so that the configuration doesn't refer to
MagmaTester altogether). What do you think?

Cheers and thanks for your work.
--
Miguel Cobá
http://miguel.leugim.com.mx