BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

C++ use of Malloc/Realloc and Free

Subject: C++ use of Malloc/Realloc and Free
From: kclark at CetaceanNetworks.com (Kevin D. Clark)
Date: 24 Jun 2003 15:07:49 -0400
In-reply-to: <20030624145713.5ecc798f.gaf@blu.org>
References: <20030624160103.5943A26F4E@asgard.blu.org> <1403.68.162.220.216.1056474024.squirrel@mail.mohawksoft.com> <20030624133526.70fee01f.gaf@blu.org> <3yn0g79w84.fsf@koan.cetaceannetworks.com> <20030624145713.5ecc798f.gaf@blu.org>

Jerry Feldman <gaf at blu.org> writes:

> If you religiously follow the standards, your code should be reasonably
> portable. Too many programmers make assumptions, like long == 32 bits
> (WRONG), endian == little (WRONG). Malloc(3) et. all should be ok in C++
> when use in the proper context. 

Ah, so we agree then -- excellent!

Regards,

--kevin
-- 
Kevin D. Clark / Cetacean Networks / Portsmouth, N.H. (USA)
cetaceannetworks.com!kclark (GnuPG ID: B280F24E)
alumni.unh.edu!kdc

Follow-Ups:
- C++ use of Malloc/Realloc and Free
  - From: gaf at blu.org (Jerry Feldman)

References:
- C++ use of Malloc/Realloc and Free
  - From: markw at mohawksoft.com (markw at mohawksoft.com)
- C++ use of Malloc/Realloc and Free
  - From: gaf at blu.org (Jerry Feldman)
- C++ use of Malloc/Realloc and Free
  - From: kclark at CetaceanNetworks.com (Kevin D. Clark)
- C++ use of Malloc/Realloc and Free
  - From: gaf at blu.org (Jerry Feldman)

Prev by Date: C++ use of Malloc/Realloc and Free
Next by Date: Commercial Wireless Access Points
Previous by thread: C++ use of Malloc/Realloc and Free
Next by thread: C++ use of Malloc/Realloc and Free
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org