in DesireData, pd_error() is now deprecated. it should be replaced by a plain error(). This is because error() can now gather much more information than the former pd_error() could ever dream of, and the new pd_error() doesn't add anything to that.
I'm currently removing all pd_error() from DesireData.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
How about make pd_error() call error() and issue a warning. Otherwise the API becomes incompatible.
.hc
On Jul 19, 2007, at 12:50 AM, Mathieu Bouchard wrote:
in DesireData, pd_error() is now deprecated. it should be replaced by a plain error(). This is because error() can now gather much more information than the former pd_error() could ever dream of, and the new pd_error() doesn't add anything to that.
I'm currently removing all pd_error() from DesireData.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada_______________________________________________ PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
------------------------------------------------------------------------ ----
Terrorism is not an enemy. It cannot be defeated. It's a tactic. It's about as sensible to say we declare war on night attacks and expect we're going to win that war. We're not going to win the war on terrorism. - retired U.S. Army general, William Odom
On Thu, 19 Jul 2007, Hans-Christoph Steiner wrote:
How about make pd_error() call error()
Sorry, I am not clear. By deprecated I mean still supported. All the pd_error()s I removed were calls, not the implementation.
and issue a warning.
If I make it issue a warning I'll get pagefuls of warnings for externals that are made to run in Pd and still need to use pd_error in order to get correct error messages in Pd. So, no warning.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
On Jul 19, 2007, at 6:21 PM, Mathieu Bouchard wrote:
On Thu, 19 Jul 2007, Hans-Christoph Steiner wrote:
How about make pd_error() call error()
Sorry, I am not clear. By deprecated I mean still supported. All the pd_error()s I removed were calls, not the implementation.
and issue a warning.
If I make it issue a warning I'll get pagefuls of warnings for externals that are made to run in Pd and still need to use pd_error in order to get correct error messages in Pd. So, no warning.
How about a compiler warning, isn't it something like #warning?
.hc
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
------------------------------------------------------------------------ ----
¡El pueblo unido jamás será vencido!
Hans-Christoph Steiner wrote:
How about a compiler warning, isn't it something like #warning?
No, that emits a warning when the #warning line is reached by the preprocessor. In GNU C you can emit warnings when deprecated functions are *used* like this:
int old_fn () __attribute__ ((deprecated));
But that's GNU C not ANSI C nor Microsoft C nor...
Claude
On Fri, 20 Jul 2007, Claude Heiland-Allen wrote:
Hans-Christoph Steiner wrote:
How about a compiler warning, isn't it something like #warning?
No, that emits a warning when the #warning line is reached by the preprocessor. In GNU C you can emit warnings when deprecated functions are *used* like this: int old_fn () __attribute__ ((deprecated)); But that's GNU C not ANSI C nor Microsoft C nor...
Thanks. DesireData depends on GNU C. That's portable enough for me.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
-
Claude Heiland-Allen -
Hans-Christoph Steiner -
Mathieu Bouchard