Re: Threaded Interpretive Languages

dsiegel@panix.com (David Siegel)
Sun, 26 Sep 1993 17:26:45 GMT

          From comp.compilers
Related articles
Threaded Interpretive Languages a_tucker@paul.spu.edu (Andrew Tucker) (1993-09-14)
Re: Threaded Interpretive Languages jvn@fermi.clas.virginia.edu (Julian V. Noble) (1993-09-21)
Re: Threaded Interpretive Languages cliffc@rice.edu (1993-09-23)
Re: Threaded Interpretive Languages N.Chapman@cs.ucl.ac.uk (Nigel Chapman) (1993-09-24)
Re: Threaded Interpretive Languages dsiegel@panix.com (1993-09-26)
Re: Threaded Interpretive Languages pop@dcs.gla.ac.uk (pop) (1993-09-28)
Re: Threaded Interpretive Languages cliffc@rice.edu (1993-09-28)
Re: Threaded Interpretive Languages mikc@gnu.ai.mit.edu (1993-09-29)
| List of all articles for this month |
Newsgroups: comp.compilers,comp.lang.forth
From: dsiegel@panix.com (David Siegel)
Keywords: design, smalltalk
Organization: PANIX Public Access Internet and Unix, NYC
References: 93-09-059 93-09-111
Date: Sun, 26 Sep 1993 17:26:45 GMT

cliffc@rice.edu (Cliff Click) writes:
> How do you do source-code-control reasonably well?
> (How do the Smalltalk folks do it?)


I've seen 3 approaches:


a. Track method changes via database updated by browser
b. Section the image, periodically 'release' a section
c. Shared image
In a sense, punt -- flush updates from your image
to all your coworkers.
Tends to get code well tested early, but occasionally
leads to major chaos as changes fly in from all directions.


-dms
--

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.