[Spread-users] sp.h defines collitions
Marcelo.San-Martin at harmonicinc.com
Thu Jun 27 12:52:43 EDT 2013
How can others help you to get there? It would be nice if contributors could help providing changes, it would require a bug tracking system.
From: John Schultz [mailto:jschultz at spreadconcepts.com]
Sent: Thursday, June 27, 2013 7:51 AM
To: Marcelo San-Martin
Cc: spread-users at lists.spread.org
Subject: Re: [Spread-users] sp.h defines collitions
In general, we agree and have been trying to move away from such things. However, these definitions have been part of the project for a long time and getting rid of these definitions now could break old code that depended on them.
We'll work on this and see if we can come up with a good solution.
John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200
On Jun 24, 2013, at 8:29 PM, Marcelo San-Martin wrote:
I don't know if there has been discussions about this file but I am having a lot of issues regarding #defines colliding with symbols, enum, and typedef defined in other libraries, for example:
# define int16 short
# define int32 int
Are these really necessary, type definitions using #define are not a good practice?
Definitions like LOW_PRIORITY and HIGH_PRIORITY are very common, Wouldn't be better to have all this prefixed with "SPREAD_" instead?
Spread-users mailing list
Spread-users at lists.spread.org
More information about the Spread-users