> > A simple compiler warning in the Transcript might work. Like we have for Undeclared and shadowed variables ... 
> 
> Ah. This is something I do not like, at least not in the simplistic sense of writing to the Transcript.
> a) may very well not have an open Transcript
> b) may be compiling code in a system where nobody could ever see a Transcript
> c) can't handle the error
> 
> A suitable exception, perhaps with a defaultAction to write to a Transcript, would be easier to live with.

+1. I would vote for a new subclass of ParserNotification - maybe let's make it configurable, but I would even prefer to get a small DialogWindow similar for "unused temp vars" etc. if I try to use a deprecated selector.

Best,
Christoph

---
Sent from Squeak Inbox Talk

On 2021-09-10T09:57:21-07:00, tim at rowledge.org wrote:

> 
> 
> > On 2021-09-10, at 1:52 AM, Marcel Taeumel <marcel.taeumel at hpi.de> wrote:
> > 
> > A simple compiler warning in the Transcript might work. Like we have for Undeclared and shadowed variables ... 
> 
> Ah. This is something I do not like, at least not in the simplistic sense of writing to the Transcript.
> a) may very well not have an open Transcript
> b) may be compiling code in a system where nobody could ever see a Transcript
> c) can't handle the error
> 
> A suitable exception, perhaps with a defaultAction to write to a Transcript, would be easier to live with.
> 
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> The substance "Hey Y'all, watch this!" is known by the state of California to be hazardous to your health.
> 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20210918/68f15465/attachment.html>