Path: utzoo!attcan!uunet!mcsun!inria!irisa!boissier
From: boissier@irisa.fr (franck boissiere)
Newsgroups: comp.lang.smalltalk
Subject: Re: Smalltalk source archives
Message-ID: <1990Jun14.100955.9152@irisa.fr>
Date: 14 Jun 90 10:09:55 GMT
References: <90164.094108MUHRTH@DB0TUI11.BITNET>
Sender: news@irisa.fr
Organization: IRISA, Rennes (FR)
Lines: 30

From article <90164.094108MUHRTH@DB0TUI11.BITNET>, by MUHRTH@tubvm.cs.tu-berlin.de (Thomas Muhr):
> the ideosyncratic programmer, not the tool for cooperate programming in teams.
> One experience is, that it is very hard to share COMPLETE sources, because of
> the sometimes radical changes in the system kernel, which you are enforced to
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

	BAD PROGRAMMING PRATICE

For everything I developped up to know I was NEVER forced to modify the kernel
of Smalltalk-80, I always had to do it in ST/V (is one superior to the other?
may be I won't argue).

My deontolgy is to never modify the base classes (except for bug fixes by
ParcPlace). The only things I put in the base classes are new methods if there
is REALLY no other place to put them. I am right know developping a new
look&feel to one of our project without modifying anyline of the original
window manager, and without disturbing it! And both styles may share the
screen while the whole thing in not stable and tuned.

About sharing code I do know ParcPlace has put pieces of code on ParcBench
unfortunately I don't have the right modem to access it, but I beleive
anyone can (with a US modem).



--
Franck BOISSIERE                        boissier@irisa.irisa.fr
Prototyping Lab Manager                 boissier@ccettix.UUCP
C.C.E.T.T.   B.P. 59                    boissier%irisa.irisa.fr@uunet.uu.net
35512 CESSON SEVIGNE CEDEX  FRANCE