Marti Maria
The littleCMS project
http://www.littlecms.com
- Original Message -
From: "Bob Friesenhahn" <[EMAIL PROTECTED]>
To: "Alexander Wilkie" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, March 31, 2006 8:21 PM
Subject: Re: [Lcms-user] BOOL
On Fri, 31
On Fri, 31 Mar 2006, Alexander Wilkie wrote:
Since a previous mail earlier today mentioned that there is apparently going
to be a new release of LCMS in the near future, I just wanted to emphasise
one request which has already been made on this list before - a re-naming of
the BOOL type.
Thi
Hi!
Since a previous mail earlier today mentioned that there is
apparently going to be a new release of LCMS in the near future, I
just wanted to emphasise one request which has already been made on
this list before - a re-naming of the BOOL type.
LCMS is a great toolkit, but for all of u
On Monday 7 February 2005 18:30, Marti Maria wrote:
> and placed into icc34.h AFAIK there are several ports of lcms running in
> 64 bit platforms without problems. Has to be seen what happens in XP64 :-)
Yes, this can be dealt with later, until after the issue of source
compatibility across 32 an
On Monday 7 February 2005 16:33, Bob Friesenhahn wrote:
> 'unsigned int' is a 32-bit quantity on 32-bit and normal 64-bit
> systems. 'unsigned long' is a 64-bit type on 64-bit systems. It
> would be fine to use 'unsigned long' on 32-bit CPUs, but whatever
> warnings you are seeing would still be
ia
The little cms project
http://www.littlecms.com
- Original Message -
From: "Hans Leidekker" <[EMAIL PROTECTED]>
To: "Bob Friesenhahn" <[EMAIL PROTECTED]>
Cc: "Marti Maria" <[EMAIL PROTECTED]>; "Lcms-User"
Sent: Monday, February 07, 2005 6:1
On Mon, 7 Feb 2005, Hans Leidekker wrote:
Actually, there may be a problem in this regard. DWORD is
defined as 'unsigned long' on Windows, Wine and MinGW whereas
lcms.h defines it as 'unsigned int'. These definitions are
compatible on 32 bit systems AFAICS, but I'm not sure about
64 bit systems. Ca
Marti Maria wrote:
I'm considering as a solution to add a conditional
#define named "LCMS_WIN_TYPES_ALREADY_DEFINED"
That would only take effect on non-windows compilation.
That could work for Wine, yes. And then use LCMS_VERSION to
find out if the header supports this.
If this special flag is de
Hi,
Thanks to all for your great feedback.
I'm considering as a solution to add a conditional
#define named "LCMS_WIN_TYPES_ALREADY_DEFINED"
That would only take effect on non-windows compilation.
If this special flag is declared, then the types:
BYTE, LPBYTE, WORD, LPWORD
DWORD, LPDWORD, BOO
t; http://www.littlecms.com
>
>
> - Original Message -
> From: "Kai-Uwe Behrmann" <[EMAIL PROTECTED]>
> To: "Lcms Liste"
> Sent: Friday, February 04, 2005 8:07 AM
> Subject: [Lcms-user] BOOL -> LCMS_BOOL
>
>
> > Marti,
> >
On Fri, 4 Feb 2005 11:32:14 +, John Cupitt <[EMAIL PROTECTED]> wrote:
> #ifdef IM_DISABLE_DEPRECATED
> #define RGB (4)
> #endif /*IM_DISABLE_DEPRECATED*/
>
> #define IM_TYPE_RGB (4)
Of course I'm an idiot, that should be
#ifndef IM_DISABLE_DEPRECATED
John
-
Hi Marti, Kai-Uwe, Hans and others,
I obviously see your point. And agree BOOL and in general all
windows-like types would pollute global namespace. My main concern
is about breaking existing code. Let's take for example the tifficc utility.
It just #includes the lcms header and then use BOOL, DW
On Fri, 4 Feb 2005 12:10:54 +0100, Marti Maria <[EMAIL PROTECTED]> wrote:
> Any thoughts? What do you think is the best move, add a LCMS_*
> prefix on all those types and label the new code as 2.0? Or just keep
> the 1.* convention until the smart CMM and gamut mapping features
> were available? O
amut mapping features
were available? Or just keep actual #defines untouched?
Regards,
Marti Maria
The little cms project
http://www.littlecms.com
- Original Message -
From: "Kai-Uwe Behrmann" <[EMAIL PROTECTED]>
To: "Lcms Liste"
Sent: Friday, February 04, 2005 8:0
On Fri, 2005-02-04 at 08:07 +0100, Kai-Uwe Behrmann wrote:
> As X is an large project, I prefere to ask You in the first place.
> Would You mind to rename the typedef BOOL in the lcms header?
This is a good opportunity for me to chime in. I am working on
implementing the msmcs api in Wine on top
Marti,
I found the
typedef CARD8 BOOL
in an X header.
As X is an large project, I prefere to ask You in the first place.
Would You mind to rename the typedef BOOL in the lcms header?
I think it is no good idea by the X project to use this type too. They
should have known that someone else w
16 matches
Mail list logo
