Re: [Chicken-hackers] [PATCH] Generalize deprecation type warnings

[Jörg F. Wittenberger]

Am 12.05.2014 21:09, schrieb Evan Hanson:

On 2014-05-12 20:54, Peter Bex wrote:

On Mon, May 12, 2014 at 11:42:26AM -0700, Evan Hanson wrote:

This is instead of "library procedures", since deprecated identifiers
need not be procedures.

But I don't see syntax identifiers as having a "value" in the traditional
sense.  How about "detected use of ~A which is deprecated"?

Hmmm, true, good call. Perhaps just this, then? Simplify, simplify,
etc.

Hm.  Great to see it's already there.

However I would not tie the message to just directing to some alternative.  IMHO it would be useful if it was more general.

To deprecate and give the "use instead" advice, one could easily write (: old-thing (deprecated "use new-thing instead")).

However I see other uses for deprecation of bindings too.  Imagine an unsolved security issue: I'd just give the ticket URL.  Or the deprecated thing needs to be replaced with rather different code, which requires more rewrite than a simple replacement: Give a link to the HOWTO or maybe explain more just in this message.

It seems one could use the current behavior just like that.  Except that the message from the compiler would look  strange.  How about shortening

"use of deprecated `~a' - consider using `~a' instead"

to

"use of deprecated `~a' - consider `~a'"

It might come along a bit terse for the normal case - as so many compiler warnings, though.

/Jörg

_______________________________________________
Chicken-hackers mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/chicken-hackers