RE: OO2C -> Debian?

[Michael van Acken <KK120y2@mail.lvr.de>]

[this message is CC'ed to ooc-list]
 
> Ok, it appears I am accepted by Debian WNPP as oo2c and gc package
> maintainer.  Please keep me posted when versions update, etc. 
Since
> you indicated that a new release of oo2c would be forthcoming in a
> few days, I will try to get gc packaged in the meantime.

Then you should subscribe to the mailing list:

  "The ooc-list mailing list has been set up as a discussion place
for
developers. To subscribe, send mail to
ooc-list-request@informatik.uni-kl.de and put the word `subscribe'
into the subject line or the body. The list is not automated, it may
take a few hours until subscription."

It is very low volume, with occasional bursts.

What about libtool?  I removed gc from the oo2c distrib, and it would
be consistant to remove the libtool stubbs as well.  I believe,
Debian
1.3 has a libtool package, but I don't know is this still exists in
2.0.

> I don't want to overcommit myself here, but I would be interested
in
> taking a look at integrating Posix threads with oo2c, since some
> variant of this should be supported on many platforms if not all
> (i.e., both LinuxThreads and NT threads can apparently be used in a
> Posix compliant fashion.)  My interest is because I use a dual-PII
> system, and I would love for the inherent concurrency of O2 to be
> exploited to the fullest on my platform.

There are a number of points to consider:

1. Which abtraction should be presented to the user?  That is, how
should the "Threads" module look like?

2. How are threads tied into oo2c's installation process?  This is
mostly an issue with configure.

3. Which library modules have to be modified to be thread safe?

The first point is open to discussion, preferably on the mailing
list.
There needs to be a common Oberon-2 interface to all threads
packages,
of course.

Once the details of support for the various threads packages are
hammered out, I will take the necessary steps to integrate threads
into the installation process.

It shouldn't be much of a problem to identify library modules that
aren't thread safe.  I will update any modules I've written myself,
but I won't touch the other modules.

-- mva
[please reply to acken@informatik.uni-kl.de, _not_ kk120y2@...]