Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Comparing productivity: LisP against C++ (was Re: Reference Counting)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Steve Haflich  
View profile  
 More options Dec 31 1994, 10:15 pm
Newsgroups: alt.lang.design, comp.lang.c++, comp.lang.lisp
From: s...@Franz.COM (Steve Haflich)
Date: Sat, 31 Dec 1994 10:24:15 GMT
Local: Sat, Dec 31 1994 5:24 am
Subject: Re: Comparing productivity: LisP against C++ (was Re: Reference Counting)
In article <3e30ag$...@wariat.wariat.org> r...@wariat.org (Robert J. Brown) writes:

   From: r...@wariat.org (Robert J. Brown)

   :    "Memory leaks are relatively easy to deal with as long as you
   :     use free() when the data pointed to will no longer be used."

   C and C++ programmers are rather proud of themselves in thinking that they
   will always know when an object is no longer being referenced by anything
   else, but the dangling reference is one of the most notorious and hard to
   find class of bugs in these programming languages!
   They just do not believe in garbage collection ...

True.  When your hammer is C++, everything begins to look like a thumb.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.