linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dalgoda@ix.netcom.com (Mike Castle)
To: linux-c-programming@vger.kernel.org
Subject: Re: [jason@txt.com: Re: Problem with "chars"]
Date: Wed, 24 Jul 2002 12:56:00 -0700	[thread overview]
Message-ID: <go0nha.u6f.ln@thune.mrc-home.org> (raw)
In-Reply-To: 20020717123023.A2248@cs.pdx.edu

In article <20020717123023.A2248@cs.pdx.edu>,
Marius Nita  <marius@cs.pdx.edu> wrote:
>It seems that this issue has become a religious thing, tho I don't see why. It
>is clear that the return of malloc need not (and must not--for correctness) be
>casted.

I believe it was necessary for pre or early ANSI C, so a lot of old code
written by some pretty smart people used it.

mrc

-- 
     Mike Castle      dalgoda@ix.netcom.com      www.netcom.com/~dalgoda/
    We are all of us living in the shadow of Manhattan.  -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc

  parent reply	other threads:[~2002-07-24 19:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 14:33 [jason@txt.com: Re: Problem with "chars"] xlp
2002-07-17 17:55 ` Elias Athanasopoulos
2002-07-17 17:55   ` Jason P. Winters
2002-07-17 18:07     ` Glynn Clements
2002-07-17 18:24       ` Jason P. Winters
2002-07-17 18:54       ` Glynn Clements
2002-07-17 18:16     ` Elias Athanasopoulos
2002-07-17 19:30     ` Marius Nita
2002-07-18 14:43       ` Earl R. Lapus
2002-07-24 19:56       ` Mike Castle [this message]
2002-07-24 21:05         ` Jason P. Winters
2002-07-24 22:38           ` Glynn Clements
  -- strict thread matches above, loose matches on Subject: below --
2002-07-18  7:11 Alvarez Alberto-AALVARB1
2002-07-18  9:25 ` Elias Athanasopoulos
2002-07-18  9:18   ` Marius Nita

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=go0nha.u6f.ln@thune.mrc-home.org \
    --to=dalgoda@ix.netcom.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).