Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!elroy.jpl.nasa.gov!swrinde!zaphod.mps.ohio-state.edu!think.com!paperboy!hsdndev!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: Whose code should we break? ( was Re: 64 bit C )
Message-ID: <15256@smoke.brl.mil>
Date: 20 Feb 91 00:04:11 GMT
References: <MARC.91Feb14085851@marc.watson.ibm.com> <1215@dms.UUCP> <65469@brunix.UUCP>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 11

In article <65469@brunix.UUCP> cgy@cs.brown.edu (Curtis Yarvin) writes:
>But I want sizeof long == sizeof char *.  There are quite a few applications
>in which I find myself writing my own memory manager; I need some type
>in which I can flick the bits on my pointers, portably.

As maintainer of several major pieces of software that did just that,
I highly DISrecommend the practice.  If you can find ANY way to let
the C implementation handle memory management sufficiently well for
your actual needs, you are far better off doing so.

Clearly bit diddling in pointers in far from portable.