[comp.lang.smalltalk] smalltalk code in news

thomas@falcon.bcm.tmc.edu (03/31/89)

May i suggest that actual code (unless a short fragment) not be
posted; rather, a description of its function and the author's email
address, so those really wanting it can request it?

new@udel.EDU (Darren New) (03/31/89)

In article <1473@gazette.bcm.tmc.edu> thomas@falcon.bcm.tmc.edu () writes:
>May i suggest that actual code (unless a short fragment) not be
>posted; rather, a description of its function and the author's email
>address, so those really wanting it can request it?

I would rather have it posted. The problems with getting EMail
to any particular site from any other are ledgendary.
Rather than having 40 people say "I would really like that,
but my mail to you bounces", I would rather have it
come through the news group. The `n' key is always available.
		- Darren

pieter@prls.UUCP (Pieter van der Meulen) (04/01/89)

In article <11904@louie.udel.EDU> new@udel.EDU (Darren New) writes:
>In article <1473@gazette.bcm.tmc.edu> thomas@falcon.bcm.tmc.edu () writes:
>>May i suggest that actual code (unless a short fragment) not be
>>posted; rather, a description of its function and the author's email
>>address, so those really wanting it can request it?
>
>I would rather have it posted. The problems with getting EMail
>to any particular site from any other are ledgendary.
........

I admit I have posted code in this newsgroup, and I also have
put notes up with a description of the software and my EMail address
(long time ago though), but did not get many responses.. 

Now I was about to post another Smalltalk-80 Goodie (a BinaryChoice and
FillInTheBlank with a time-out mechnism), but should I do it?

You can consider this also as a note, and can EMail me your requests.
And, of course, if you can't reach me via EMail, you can always
respond to it in this newsgroup :-)

Pieter.

-- 
---------------------------------------------
P.S. van der Meulen, MS 02        prls!pieter
PRLS, Signetics div. of NAPC      -----------
811 E.Arques Avenue, Sunnyvale, CA 94088-3409

voss@s.cs.uiuc.edu (04/01/89)

>>May i suggest that actual code (unless a short fragment) not be
>>posted; rather, a description of its function and the author's email
>>address, so those really wanting it can request it?

>I would rather have it posted. 

	I definitely 2nd the motion.
	Unless the code is more than about 10 pages POST IT.
	(If you can't post it anonymous FTP is also OK for me.)

>The `n' key is always available.

	definitely.

obrien@anpiel.aero.org (Mike O'Brien) (04/03/89)

In article <20591@prls.UUCP> pieter@prls.UUCP (Pieter van der Meulen) writes:
>
>Now I was about to post another Smalltalk-80 Goodie (a BinaryChoice and
>FillInTheBlank with a time-out mechnism), but should I do it?

I'm rather surprised to see this discussion, really.  As far as I'm
concerned, the answer is: Yes, absolutely, post any source you want
to.  As long as it's not proprietary to anyone, post little things,
huge things (batched in several messages), whatever.  This group is
here to help people, and goodies are some of the best help you can
get.

If (oh happy day!) source begins to clog up the newsgroup too much,
then we stump for the creation of "comp.lang.smalltalk.sources", shove
all the source in there (moderated, probably), and go on with
discussions as usual right here.

Personally, I don't think there's too MUCH source here, I think there's
too LITTLE.
--
Mike O'Brien
obrien@aerospace.aero.org
{sdcrdcf,trwrb}!aero!obrien

uucigj@sw1e.UUCP (3531]) (04/04/89)

I too would like to see a bit of source.  I am new to smalltalk (just
getting into smalltak/V 286), and I would like to see as many examples as 
possible.  There are not very many places where I can receive information
about smalltalk, this being one of the main ones.  This is a wonderful
resource for information and to not allow source code to be posted would
seem very detrimental to this group.