| RE: [AD] Why aren't BITMAP * parameters const where appropriate? |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: <alleg-developers@xxxxxxxxxx>
- Subject: RE: [AD] Why aren't BITMAP * parameters const where appropriate?
- From: "Robert Ohannessian" <ROhannessian@xxxxxxxxxx>
- Date: Sat, 8 Jan 2005 22:31:58 -0800
- Thread-index: AcT2DKQo6Fn9L43GREWlWC5GFMk71gACLxqg
- Thread-topic: [AD] Why aren't BITMAP * parameters const where appropriate?
See this post:
http://www.allegro.cc/forums/view_thread.php?_id=446166#target
-----Original Message-----
From: alleg-developers-admin@xxxxxxxxxx
[mailto:alleg-developers-admin@xxxxxxxxxx] On Behalf Of
Daniel Schlyder
Sent: Saturday, January 08, 2005 9:18 PM
To: alleg-developers
Subject: [AD] Why aren't BITMAP * parameters const where appropriate?
Is there any reason why bitmap_color_depth()'s parameter couldn't be
made
const? And ditto for stretch_bitmap()'s 'source' parameter? And probably
lots of other functions' parameters too. The lack of const'ness means I
have
to use const_cast in my C++ program to squelch warnings from GCC.
--
Daniel Schlyder
http://bitblaze.com/
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
--
https://lists.sourceforge.net/lists/listinfo/alleg-developers