>-----Original Message-----
>From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] 
>Sent: 15 February 2005 14:03
>To: Microcontroller discussion list - Public.
>Subject: RE: [PIC] Bug in Microchip mcc18 std library?
>
>
> 
>
>I really wouldn't like the idea of not distinguishing the difference
>between the two types of pointer. They *are* different, and IMHO a
>compiler "hack" to make them compatible is a recipe for disaster.
>
>For a start, rom pointers are *always* const, ram pointers need not be.
>And think of the utter mess of trying to deal with 
>pointers-to-pointers,
>ie. void **. Eugh.


In Hitech the only type of pointer that can point to both data and
program memory are pointers to const data types.  Are you saying it's
preferable to have two different functions to deal with pointers to
data/program memory rather than one function that can work with either?
e.g. puts() which is used by printf etc.  As sson as you start splitting
things up like this the compiler moves away from ANSI compatibility and
you have to add all sorts of kludges to get things working.

Regards

Mike

=======================================================================
This e-mail is intended for the person it is addressed to only. The
information contained in it may be confidential and/or protected by
law. If you are not the intended recipient of this message, you must
not make any use of this information, or copy or show it to any
person. Please contact us immediately to tell us that you have
received this e-mail, and return the original to us. Any use,
forwarding, printing or copying of this message is strictly prohibited.
No part of this message can be considered a request for goods or
services.
=======================================================================

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist