Path: news.cs.au.dk!news.net.uni-c.dk!arclight.uoregon.edu!logbridge.uoregon.edu!dispose.news.demon.net!demon!colt.net!news0.de.colt.net!news-fra1.dfn.de!news-koe1.dfn.de!news.ruhrgebiet.individual.net!Informatik.Uni-Dortmund.DE!news
From: Holger Tuerk <htuerk00@marvin.informatik.uni-dortmund.de>
Newsgroups: comp.lang.beta
Subject: Networking ...
Date: Mon, 31 May 1999 15:39:16 +0200
Organization: CS Department, University of Dortmund, Germany
Message-ID: <37529104.2BE9@marvin.informatik.uni-dortmund.de>
NNTP-Posting-Host: marvin.cs.uni-dortmund.de
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.6 sun4u)
CC: htuerk00@marvin.informatik.uni-dortmund.de
Lines: 29
Xref: news.cs.au.dk comp.lang.beta:11973

Hello,

i am wondering about networking and components in the MBS.

Since our CASE tool (Maybe you already heard of the infamous BON/Kogge.)
does not know about components, and therefore about references to these
as parts of an enter/exit-list, the manual labour of performing the
adequate corrections to the code skeleton can be a very annoying
procedure.
  Inserting ...->componentToObject->qua(# as::blah #)->... a hundred
times ist bothersome, too.

The compiler does not accept a simple assignment a[]->b[], when a is a
component of some pattern, and b is such an object.
  Besides objectToComponent and componentToObject from the sysutils, are
there any other possibilities to handle the difference, or to convert
the ones into the others?

Are there any pitfalls in using objectToComponent and componentToObject
that my fellow students and me should have heard of?

Are the patterns from the container library tuneable to manage
components instead of objects?

Thanks in advance.

Greetings,

Holger