HDTenEightyP/NetNews huggingface dataset:
From: armando@hp9k.lag.itesm.mx (Armando Ibarra Medina)
Newsgroups: comp.lang.c
Subject: Help in porting c progams to mac
Date: 28 Sep 92 16:11:42 GMT


WE ARE SOFTWARE DEVELOPERS HERE  IN MEXICO, OUR SOFTWARE IS IN DOS,
BUT NOW WE WANT TO USE  IT IN MAC, AND WE ARE NOT FAMILIAR WITH SUCH 
ENVIROMENT, SO WE ARE ASKING FOR ADVISE ON THE NEXT SUBJECTS:

A) COMPILER
WE ARE USING THE MICROSOFT C COMPILER VERSION 6.0 ,
WHICH COMPILER IS THE MOST COMPATIBLE IN THE MAC WITH THIS ONE?

B) LINKING
WE USE THE POCKET SOFT'S RT-LINK TO LINK OUR PROGRAMS,
WE WANT TO KNOW IF THERE IS SOME SIMILAR LINKER PROGRAM ,
OR WHICH ONE IS THE MOST RECOMENDED.

C) PROTECTION
AS YOU KNOW WE HAVE A SERIOUS PROBLEM HERE AT MEXICO WITH PIRACY,
SO WE ARE USING COP'S COPY LOCK II TO PROTECT OUR SOFTWARE,
WHAT DO YOU RECOMEND TO USE IN MAC?

YOU CAN CONTACT US AT mcastro@hp9k.lag.itesm.mx,
WE'LL BE GRATEFUL ON ANY HELP OR COMMENT YOU PROVIDE TO US.
Newsgroups: comp.lang.c
From: "hans friedrich steffani" <GM08@DKAUNI2.BITNET>
Subject: Re: C-formattors (problems with very long lines)
Organization: University of Karlsruhe, Germany
Date: Wed, 30 Sep 1992 14:28:11 GMT

>
>    Can somebody tell me why the following gives the error below,
> #include <stdio.h>  /* i've also tried #include "stdio.h" */
> #include <math.h>  /* i've also tried #include "math.h" */
>
> main()
> {
>    double answer;
>
>    answer = sqrt(10.0);
>    printf("%f", answer);
> }
>
using c you ve to know that there are TWO steps
building an .exe-file or something equivalent.
first compiling and than linking.
compiling has 2  steps:
precompiling and compiling:
precompiling puts comments away and also does most
of the things with # in the first column. so the
#include is something like a editor-command wich
changes SOURCE-code. this works or it doesnt and
you are told if it does not. so changing <> to ""
does not help. (hope you had a look to th .h-files
to see that there is no realy code.)
than the compiling starts and it will work or it
wont and the compiler will tell you what went wrong.
but in your case precompiling and compiling was
ok.

than have a look to linking.
sometimes you have only one c-/source- module but
most times you have several ones.
you also get with your compiler (normaly) some liberies
-wich is only a differen way to store objectcode- with
some machinedpending fungktions like printf() or sqrt()
i think your error is that the linker didnt get the math
libary to link sqrt(). (dont worry abt. the leading _)
so have a look at your LIB-enviroment or the arguments
in commandline or so.

>   error is:
>
> Undefined:
> _sqrt
>
>      Sorry if this is incredibly obvious, but know one in my lab
>      uses C.
>
>          Dave
>          Email please: phd85@uk.ac.keele.seq1
> --
> Dave.
> phd85@uk.ac.keele.seq1

PS:
PLEASE if you ve problems tell us the name of your system
and of your compiler.

hans friedrich steffani
uni-karlsruhe
From: mansour@mu.nsc.com
Newsgroups: comp.lang.c
Subject: test
Summary: test
Date: 30 Sep 92 23:39:16 GMT
Organization: National Semiconductor, Santa Clara
Originator: mansour@mu.nsc.com

This is a test, so don't reply.
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c
Subject: Re: Question about DIR/ALLwriting binary files to mo
Date: 29 Sep 92 00:00:48 GMT
Organization: negligable

Sorry, the "rw" was older compilers -- I keep tripping myself up
on that whenever I have to get read/write access now (old habits
die hard).  Fortunately I don't have to do that very often.....



		-Richard Hartman
		hartman@ulogic.COM

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Who knows what evil lurks in the hearts of men?"
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c
Subject: Re: Memory leak detectors: references?
Keywords: References to publications on memory leak detectors
Date: 30 Sep 92 17:56:38 GMT
Article-I.D.: ulogic.333
Organization: negligable

I believe a couple of macro sets have been published in the
computer magazines -- Dr. Dobbs Journal comes to mind.

I think they are available in the DDJ forum on CompuServ,
but I couldn't tell you the issue date....


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
And when you stop and think about it	|
(you won't believe it's true)		|	-Richard Hartman	
That all the love you've been giving	|	hartman@uLogic.COM
has all been meant for you.		|
From: mcastro@hp9k.lag.itesm.mx (Manuel Castro Trevino)
Newsgroups: comp.lang.c
Subject: help on porting
Summary: help on porting
Keywords: help on porting
Date: 1 Oct 92 00:37:11 GMT


we are software developers here in mexico,our software is in DOS,
but now we want to use it in Mac and Unix/Xenix, and we are not familiar
with such
enviroment, so we are asking for advise on the next subjects:

a) compiler
we are using the microsoft C compiler version 6.0 ,
which compiler is the most compatible in Mac or  Unix/Xenix with this one?

B) linking
we use the pocket soft's rt-link to link our programs
we want to know if there is some similar linker program ,
or which one is the most recomended.

C) protection
as you know we have a serious problem here at mexico with piracy,
so we are using cop's copy lock II to protect our software,
what do you recomend to use in mac or in :unix/xenix?

you can contact us at mcastro@hp9k.lag.itesm.mx,
we'll be grateful on any help or comment you provide to us.

Manuel  Castro
Newsgroups: comp.lang.c
From: fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON)
Subject: Re: Curses to write to stderr, possible?
Organization: Computer Science, University of Melbourne, Australia
Date: Fri, 2 Oct 1992 19:09:09 GMT

hartman@ulogic.UUCP (Richard M. Hartman) writes:

>If you can isolate the curses stuff in subroutines you could
>always play games w/ the file pointers....
>
>
>	displaySomething(...)
>	{
>	FILE *old = stdout;
>	stdout = stderr;

Note that this scheme will not work with most K&R C compilers, and I
suspect that many ANSI C compilers might still reject it, because
stdout is usually #defined as something like &__iob[1].

-- 
Fergus Henderson             fjh@munta.cs.mu.OZ.AU      
This .signature virus is a self-referential statement that is true - but 
you will only be able to consistently believe it if you copy it to your own
.signature file!
Newsgroups: comp.lang.c
From: mike@taumet.com (Mike Ball)
Subject: Re: Is there is (pascal) WITH equivalent in C?
Organization: TauMetric Corporation, San Diego
Date: Fri, 2 Oct 1992 12:43:50 GMT

In article <1992Oct2.073814.27698@organpipe.uug.arizona.edu> dave@cs.arizona.edu (Dave Schaumann) writes:
>[geeze! doesn't anyone take compiler writing classes any more?]
>
>Pascal's with statement is nothing more or less than syntactic sugar.

geeze!  doesn't anyone learn a language before commenting on it? :-)

The with statement is exactly as much "syntactic sugar" as reflexive
operators in C are syntactic sugar.

The with expression is evaluated exactly once, which has semantic
consequences exactly similar to the fact that the lhs of a reflexive
operator is evaluated once.

That being said, in the case of a simple qualification a.b.c, it would
indeed be evaluated at compile time and have no practical effect beyond
causing hard-to-find scoping errors.
-- 
Michael S. Ball (mike@taumet.com)
TauMetric Corporation
From: bjones@pbs.org
Newsgroups: comp.lang.c
Subject: Help! Need database report libraries
Date: 2 Oct 92 22:47:41 GMT
Organization: PBS:Public Broadcasting Service, Alexandria, VA


Hi all!

Can any of you seasoned C language programmers recommend
a package of library routines that can facilitate
generating printed reports (ASCII) from a custom-developed
database? To clarify further - this is NOT an SQL
database and it runs on an IBM PC under DOS. The only 
requirement is that the library be documented and
supported. 
Thanks in advance for ANY suggestions!

Beata
-- 
***************************************************
	Beata Jones	bjones@pbs.org
***************************************************
Newsgroups: comp.lang.c
From: u8903845@cs.uow.edu.au (Anil Sachdeva)
Subject: Inferface Tools For PC ?
Organization: Dept of Computer Science, Wollongong University, Australia
Date: Sat, 3 Oct 1992 07:40:11 GMT

Hi

I am planning to buy some Interface Tool, which develops
Interface code in C and the relevant makefiles etc 
for PC
^^^^^^

What about it's ability to generate Interface for Dos and Windows .

Is the Code produced Portable, Like Using on the Macintosh as well .
I know their are some tools around like Vitamin C.

Actually i am using DEVGUIDE on Sun SPARC station .
I really enjoy using it , because it makes developing
the interface so easy , I use it's Connection manager to specify
the function associated with Interface elements and it generates the 
prototype as well. I just simply go their and insert my code in the function .

I will post the summary on net.

Thanks

Anil

u8903845@cs.uow.edu.au
Newsgroups: comp.lang.c
From: dkeisen@leland.Stanford.EDU (Dave Eisen)
Subject: Re: Getting file attribute from SunOS
Organization: Sequoia Peripherals, Inc.
Date: Sun, 4 Oct 92 22:54:16 GMT

In article <1992Oct4.191201.1990@hyphen.com> dwight@hyphen.com (Dwight Ernest) writes:

>There are three different timestamps available in most UNIX implementations:
>creation time, access time, and modification time.  All three are available
>with the 'stat()' call.  You can read more about it in section 2V of the
>manual.

The three timestamps in UNIX are access time, modification time, and
inode change time. Creation time is not kept.



-- 
Dave Eisen    dkeisen@leland.Stanford.EDU   Sequoia Peripherals: (415) 967-5644
      There's something in my library to offend everybody.
        --- Washington Coalition Against Censorship
Newsgroups: comp.lang.c
From: cuffell@spot.Colorado.EDU (CUFFELL TIMOTHY MICH)
Subject: Re: Freeing dynamic allocated memory
Organization: University of Colorado, Boulder
Date: Tue, 6 Oct 1992 09:08:33 GMT

In article <92278.164951U37956@uicvm.uic.edu> <U37956@uicvm.uic.edu> writes:
>Suppose I dynamically allocated a chunk of memory using malloc() in a function,
>but I do not free it when exiting the function. Will the system automatically
>do the garbage collection for me? If not , can I use the original data in the
>memory if the function is re-entered ?

No.  In fact, most data structures depend on this fact.  I you wanted to add
another item to an existing structure, a function would allocate the memory
and do this.  If you wanted to remove and item from an existing data structure,
a function would perform the necessary free()'s while removing it.  You have
to make sure the pointer pointing to the newly malloc()'ed space doesn't get
scoped away when you exit the function, because the malloc()'ed space will
still exist even if nothing is pointing to it, and you can't get to it.

The only garbage collection I know of C doing is releasing everything after the
program finished executing.  Everything else is left to the user.

>This is a question I have been wondering for a long time. Maybe some of you
>think it is a very easy problem.

Maybe it's easy now that I am a senior CS major.  I know it wasn't a year ago.



Xref: sparky comp.lang.c:14602 comp.sources.wanted:4576 comp.msdos.programmer:67 comp.misc:3897
From: hollen@megatek.UUCP (Dion Hollenbeck)
Newsgroups: comp.lang.c,comp.sources.wanted,comp.msdos.programmer,comp.misc
Subject: Re: Wanted: C-isam library for Turbo C or Microsoft C
Date: 6 Oct 92 20:21:10 GMT
	<BvMK7v.664@ais.org>
Organization: Megatek Corporation, San Diego, California

>>>>> On 5 Oct 92 01:31:05 GMT, draper@ais.org (Patrick Draper) said:

Patrick> In article <1992Oct2.132840.27055@jmp.com> gbm@jmp.com (Gary McKenney) writes:
>In article <1992Sep30.171329.10078@di.unipi.it> Nico Tranquilli <@> writes:
>>Does anyone have (or know where to find) C-Isam libraries for
>>Microsoft C 6.00 or Turbo C 2.0 compiler ?
>
>A good set of routines is C-Tree from FairCom.  
>
>Code is very portable and reliable.  I've been using it for years.
>(There, you have my testimonial..)
>
>You can order it through Programmer's Paradise for $476.00
>1-800-445-7899
>
>Gary McKenney 

Patrick> Also, try Mix Software's 20 dollar database toolchest. I've
Patrick> heard good reviews of that, although I have no personal
Patrick> experience. The price is certainly right.

I have been using it for about 3 years now and am very satisfied.
Comes with the best documentation you have seen (this is a general
comment about anything from MIX, also).  For a few dollars more, you
can even get source code, which I did.  It is implemented as a B-Tree
library and on top of that the ISAM.  Thay way, if you want to use the
B-Tree stuff by itself, it is available directly.  Also in source is
the Little Data Manager, kindof like the dBASE assistant, only not
quite as broad in functionality.  Also several utilities to convert
back and forth from/to dBASE format.  

The only drawback with the Database Toolchest is the format of the
files.  Fields and records are variable length, completely, and as
such are delimited with a binary zero.  Because of this, you cannot
store a binary zero as the contents of a field.  This will force you
to use conversion functions if you want to store numbers.  What I
found is that when you go to a user interface of most any kind, you
get the user edited number back as a string anyway, so I just carried
all numbers around as strings.  The application I am using it with
does not ever need to do math on numbers, so it is not a problem.

In all this time, the only problems I have had with the package have
been through being a stupid programmer and doing something which
would corrupt either the indexes or the database.  Once I got my
programming straightened out, then the corruption problems never again
surfaced. 

This is an excellent package and for the price, puts it in the
catagory of AWESOME!!!!

-- 
Dion Hollenbeck       UUCP: {uunet, ucsd, sun}!megatek!hollen
                      INTERNET:            hollen@megatek.com
Megatek Corporation  9645 Scranton Rd.  San Diego, Ca.  92121
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c
Subject: Re: ++i = i++ ?
Date: 30 Sep 92 00:35:14 GMT
Organization: negligable

In article <1992Sep28.162405.29567@fzi.de> fzi.de writes:
>I wanted to use the statement: 
>       
>       for (i = 0; i < Count, ++i)
>       { /*any correct c codes*/}
>
>Then I made a typo by writting down "i++" instead of "++i" ...
>
>The result: both of them are functioning (offer the same result)!
>
>Someone there could enlighten me on this?

Item #1: typo, "," between "Count" and "++i" should be a ";"
	(I assume that your code has it right....)

Item #2: in this context "++i" and "i++" do the same thing.
	the prefix "++i" increments the variable then performs
		the rest of the statement;
	the postfix "i++" performs the rest of the statement then
		increments the variable.

	in the case of the "post loop statement" part of the for
	loop, there is no difference, since there really IS no
	"rest of the statement" to evaluate, the only thing you're
	doing IS incrementing the variable.

	Where this difference becomes a difference is in statements
	like this:

		a = b++;
	vs.
		a = ++b;

	let's say that b starts w/ the value of '3', after the first
	statement, a will have the value of 3 and b will have the 
	value of 4, after the second statement both a and b will have
	the value of 4.  I won't bother getting into nasty stuff
	like "a++ = ++b;"......

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
But I am frightened for you, children,		|
that the life that we are living is in vain,	|	-Richard Hartman	
and the sunshine we've been waiting for		|	hartman@uLogic.COM
has turned to rain....				|
From: dat@thinkage.on.ca (David Adrien Tanguay)
Subject: Re: Differences between ANSI C and VAX C
Organization: Thinkage, Ltd.
Date: Mon, 5 Oct 1992 17:45:45 GMT

mad@spirit.clearpoint.com (Michael Davis) writes:
[ANSI C vs. VAX C]
>I hope I'm not too late to be of use--I don't read comp.lang.c very
>often.  Anyway, one thing that bit me is that global variables are all
>UPPERCASED during compilation.  If you have a function FooBar and a
>variable foobar, which should be distinct, VAX C will barf.

ANSI C does not guarantee that FooBar and foobar are distinct for *globals*.
Six case-indistinct characters are all that are guaranteed, although an
implementation may provide case distinction and longer names.
-- 
David Tanguay       dat@Thinkage.on.ca  dat@Thinkage.com  uunet!thinkage!dat
Thinkage, Ltd.           Kitchener, Ontario, Canada          [43.40N 80.47W]
Xref: sparky comp.lang.c:14153 comp.lang.c++:14209
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c,comp.lang.c++
Subject: Re: How Do I Create Word-Wrap in C or C++ (Borland 2.0)?
Date: 26 Sep 92 20:53:20 GMT
Followup-To: comp.lang.c
Distribution: na
Organization: negligable

If the character is past the margin & not a whitespace count backwards
in you array until you find a whitespace.  end your display line there
and start the next one w/ the start of the word (which you just found
by looking backwards for a whitespace...)

Real basic.  You can add all the bells and whistles yourself.


		-Richard Hartman
		hartman@uLogic.COM

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Extensive studies have shown that 93% of all statistics are meaningless.

Newsgroups: comp.lang.c
From: alpha@waggen.twuug.com (Joe Wright)
Subject: Re: Novice question about memory allocation
Organization: ALPHA, Box 68621, Va. Beach, VA 23455
X-Newsreader: TIN [version 1.1 PL6]
Distribution: usa
Date: Fri, 25 Sep 1992 16:54:23 GMT

Georg S. Nikodym (georgn@noweh.com) wrote:
: In article <1992Sep18.074916.5156@newstand.syr.edu> wender@top.cis.syr.edu (Elaine Wenderholm) writes:
: >Could someone please tell me how to allocate memory for a multidimensional
: >array?
: 
: I'll answer this with a question.  If you have a line of code:
: 
: 	int foo[10];
: 
: Where does the memory for it come from?
: 
: So by not so obvious extension, a multi-dimensional array is much the
: same:
: 
: 	int bar[10][10];
: 
: Now things get more interesting when you want to use dynamic memory
: allocation.  I direct you to the manual pages for malloc(3) and friends.
: 
: >The books I have don't discuss it, and an example recently posted here
: >did not work.
: 
: _Advanced C - Tips and Techniques_ by Paul & Gail Anderson (Hayden Books)
: covers this stuff and more.
: 
: >Is there an FAQ list?
: 
: Yup, it's posted here periodically.  You should also be able to find it
: in the news.answers group.
: 
But to answer the question, assume an array 'int foo[100][10]' but you
would allocate it dynamically.  The above declaration of foo is read:
'array 100 of array 10 of int'.  First, declare a pointer to array 10
of int..

	int (*foo)[10];

Now allocate space for the entire array, clearing it to zero.

	foo = (int(*)[10])calloc(100 * sizeof(*foo));

Now use foo with subscripts as you will.  foo[0..99][0..9].
-- 
Joe Wright  alpha@waggen.twuug.com  alpha@wyvern.twuug.com
Newsgroups: comp.lang.c
From: wilson@glitch.cs.jhu.edu (Dwight Wilson)
Subject: Re: Strings and integer sizes
Organization: The Johns Hopkins University CS Department
Date: Fri, 2 Oct 1992 23:01:36 GMT

In article <9227705.8771@mulga.cs.mu.OZ.AU> fjh@munta.cs.mu.OZ.AU (Fergus James HENDERSON) writes:
>pjh@mccc.edu (P. J. Holsberg) writes:
>
>>(T or F) The ANSI Standard for C guarantees that
>>	sizeof(short) <= sizeof(int) <= sizeof(long)
>
>True.

I was just browsing through the Standard earlier today, and 
interestingly enough, it doesn't explicitly state this anywhere.  
(Or more accurately, if it does, I overlooked it and would appreciate
a reference to the section).

What it does state is that the values taken by a short are
a (possibly non-proper) subset of the values taken by an int
which are a (possibly non-proper) subset of the values taken
by a long (I don't have the Standard with me at the moment
so this not an exact quote).  

This would seem to imply that that the sizes are non-decreasing,
but actually it doesn't.  Presumably a 'short' could occupy more
bits than an 'int', with many bit patterns defining the same value
or being undefined.  I'm not claiming that this is a reasonable
thing to do, only that I don't see it explicitly forbidden by
the Standard.

-Dwight
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c
Subject: Re: problem with format of while, for if, and nested ifs
Date: 2 Oct 92 16:49:35 GMT
Organization: negligable

In article <BvF5Gx.ELr@research.canon.oz.au> andy@research.canon.oz.au (Andy Newman) writes:
>hartman@ulogic.UUCP (Richard M. Hartman) writes:
>>Now, let's see about syntax problems...
>>
>>>while ( condition )
>>>   {
>>>   for ( condition )
>>
>>//- problem: syntax for "for" is "for (statement; condition; statement)"
>>//		a simple "for (condition)" may have unpredictible results
>>
>
>Interesting "for" syntax, I always thought it was...
>
>	"for ( expression; expression; expresion )"
>
>With your one does that mean I can "for ( for (;;);  ; x ; if (y ) z )" ?
>					          ^ big ambiguity there!
>(Big smiley :-)
>

Sorry for not being more exact here.  I was attempting to address what
the stuff between the ('s and ;'s was supposed to be for, as opposed to
what would be specifically legal there.  But even at that I should have 
said:
	for (init; condition; follow-up)
		body;

or some such.  You are correct, in the syntax description language
a "statement" is an entirely different animal from an "expression".
However:
	for ( anything )

w/o the two ;'s is definately a problem.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
But I am frightened for you, children,		|
that the life that we are living is in vain,	|	-Richard Hartman	
and the sunshine we've been waiting for		|	hartman@uLogic.COM
has turned to rain....				|
From: hartman@ulogic.UUCP (Richard M. Hartman)
Newsgroups: comp.lang.c
Subject: Re: Probably a simple realloc() question
Date: 2 Oct 92 16:44:23 GMT
Organization: negligable

In article <23779@alice.att.com> ark@alice.UUCP () writes:
:In article <358@ulogic.UUCP> hartman@ulogic.UUCP (Richard M. Hartman) writes:
:
:> We aren't suggesting it should be forced to return successfully, we
:> are suggesting that it be forced to do it's job.  There is no reason
:> for downsizing a dynamically-allocated block of memory to fail.
:
:Sure there is.
:
:Suppose you're implementing C on top of an operating system that
:already provides malloc and free but not realloc.  Suppose further

That's not OS, but support library.  Complain to the vendor (the
original suggestion that started this mess of replies).

:Suppose further that your system provides no way to shrink the size
:of an allocated block.  If your user requests such shrinkage, you
:really have only two choices:
:
:	1. Don't return any memory to the system, but lie and tell
:	   the user you did, or
:
:	2. Allocate new memory, copy the stuff, then free the old.

	3. If you cannot allocate new memory do NOT free the old
		and return the original pointer.

:While I won't argue that (2) is always the best strategy, is is
:surely best sometimes.  The reason is that if you take a big area
:and turn it into a tiny one, you use a little extra memory for a
:while but then make a whole bunch of memory available for reuse
:
:But that implies that realloc may sometimes fail.  Oh well, that's life.

There is *never* any reason that realloc() _to_downsize_ should lose
your data.  You may not get a smaller block, but you should NOT lose
any data or get an invalid pointer.  Sizing up, of course, is a different
matter.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
But I am frightened for you, children,		|
that the life that we are living is in vain,	|	-Richard Hartman	
and the sunshine we've been waiting for		|	hartman@uLogic.COM
has turned to rain....				|
Newsgroups: comp.lang.c