February 20, 2018 Re: Annoyance with new integer promotion deprecations | ||||
---|---|---|---|---|
| ||||
Posted in reply to Jonathan M Davis | On 2/18/18 3:01 PM, Jonathan M Davis wrote: > On Sunday, February 18, 2018 19:42:07 Johan Engelen via Digitalmars-d wrote: >>> There are hundreds of lines I need to molest to make the >>> compiler shut up. I won't type another line of code on my >>> colour library until this noise is gone... I will not maintain >>> it. I am emotionally incapable of assaulting my code with those >>> casts. >> >> Using the `-transition=intpromote` compile flag is no option for >> you? > > Since that's a transition flag, it's really only a stop-gap solution. So, if > his issue is that he doesn't like having the casts in his code as opposed to > not wanting to deal with updating his code right now, the flag really > doesn't help. No, -transition=intpromote is not stopgap, it's a flag to switch behavior to the new way. The stopgap is simply that you need to use the switch to get the new behavior (eventually, you will not need the switch). Everyone who is receiving these warnings should address each one, and THEN always compile their code with -transition=intpromote. Then, you may actually be able to remove some of the casts. But you will still need casts in many cases. However, there is one case where I think even without the intpromote flag is sent, that only a single cast should be necessary: byte b = byte.min; b = cast(byte)-b; This is the same value whether you use intpromote or not. But this prints the deprecation unless you do: b = cast(byte)-cast(int)b; Which is awful. -Steve P.S. yes, Walter, I created a bugzilla for this :) https://issues.dlang.org/show_bug.cgi?id=18380 |
February 20, 2018 Re: Annoyance with new integer promotion deprecations | ||||
---|---|---|---|---|
| ||||
Posted in reply to Steven Schveighoffer | On 2/20/2018 6:23 AM, Steven Schveighoffer wrote:
> P.S. yes, Walter, I created a bugzilla for this :)
> https://issues.dlang.org/show_bug.cgi?id=18380
You da man, Steve! :-)
|
February 20, 2018 Re: Annoyance with new integer promotion deprecations | ||||
---|---|---|---|---|
| ||||
Posted in reply to Nick Sabalausky (Abscissa) | On 19 February 2018 at 21:16, Nick Sabalausky (Abscissa) via Digitalmars-d <digitalmars-d@puremagic.com> wrote: > > On 02/19/2018 03:52 AM, Manu wrote: >> >> On 18 Feb. 2018 10:25 pm, "Walter Bright via Digitalmars-d" < digitalmars-d@puremagic.com> wrote: >> >> On 2/18/2018 7:52 PM, Nick Sabalausky (Abscissa) wrote: >> >>> Well, it's also the world's most inconsistant and statndards-disregarding. We're talking 1990's MS-level behavior here. It's *always* causing trouble for something or another. >>> >> >> And the great thing about NNTP is that the user gets to choose the client. Not the server. If you don't like the way your client behaves, use another one. >> >> >> Except in this case it's you that doesn't like the way my mail client behaves. >> > > Because your mail client is BROKEN. 1. The mailing list shouldn't mail out peoples personal email addresses. I shouldn't have had Walter's personal email address anywhere near the reply-to field. All I did was click reply. If I was subscribed to a mailing list that sent my private email address to all recipients, I'd be very angry (I guess I am!). 2. It's completely normal for email clients (not just gmail) to send the text + html version of emails. Outlook does it too. If the mailing list/newsgroup synchroniser doesn't want the html it receives from email clients, it could easily truncate it, and the problem would cease to exist. > Then petition *Google* to fix their shitty fucking software. You've already been told it has fuck all to do with NNTP. > > Seriously, why the fuck would ANYONE think that by relying on Google software they're somehow NOT being dragged along by the ear on Google's every whim and misstep. Christ, we've already been through all this SAME EXACT shit in the 90's with Microsoft, let's try actually *learning* from it and move on. I'm not sure there's anything wrong with gmail here. It replied to Walter's personal email because it was in the email header... that's the bug, not my mail client. I'd say it's a critical privacy violation bug too. And emailing in HTML is the normal kind. Setting to plaintext is the un-usual configuration, and it's not a gmail/outlook bug that I don't change the mode. (it may be a gmail bug that the setting resets occasionally though, I'm not sure why it resets from time to time) If we don't want people to subscribe to the mailing list and use their email clients to interact with the newsgroup, then don't offer the mailing list: http://lists.puremagic.com/cgi-bin/mailman/listinfo/digitalmars-d Just remove and disable it, and people won't use email clients. But don't say it's invalid for people to use the interface provided in the usual way with normal/overwhelming-common email clients in default settings... |
Copyright © 1999-2021 by the D Language Foundation