From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id BFAB9211B3 for ; Thu, 29 Nov 2018 22:15:51 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 74B50121582; Fri, 30 Nov 2018 07:15:49 +0900 (JST) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by neon.ruby-lang.org (Postfix) with ESMTPS id 22C88121582 for ; Fri, 30 Nov 2018 07:15:32 +0900 (JST) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 3C1A9211B3; Thu, 29 Nov 2018 22:15:30 +0000 (UTC) Date: Thu, 29 Nov 2018 22:15:30 +0000 From: Eric Wong To: ruby-core@ruby-lang.org Message-ID: <20181129221530.qfzrnx6vuh6s6ydv@dcvr> References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-ML-Name: ruby-core X-Mail-Count: 90176 Subject: [ruby-core:90176] Re: [Ruby trunk Feature#14915] Deprecate String#crypt X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" mame@ruby-lang.org wrote: > IMO, documentation is not enough. A warning may annoy a user, > but sudden removal (in future) is much worse. There should never be a sudden removal. Honestly, I don't think we should make the first move on this issue until more-widely used projects (e.g. glibc) start warning or deprecating on it. > As a first step, how about `rb_warning` instead of `rb_warn`? It prints a warning only when $VERBOSE is enabled. A well-mannered developer can be aware of the deprecation, will fix the issue, and may even write how to fix in stackoverflow. A non-programmer user won't be annoyed. It's better, I suppose. I don't know if we can guarantee $VERBOSE isn't widely-used by some programs?