From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id B06F317D5675 for ; Tue, 28 Jan 2014 14:52:30 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id C9C86B5D847 for ; Tue, 28 Jan 2014 14:39:06 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 633A397A826 for ; Tue, 28 Jan 2014 14:39:08 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OqT2m5ntxW76 for ; Tue, 28 Jan 2014 14:39:07 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id DD1B197A820 for ; Tue, 28 Jan 2014 14:39:07 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 7000095241A for ; Tue, 28 Jan 2014 14:39:06 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 7CF291204EB; Tue, 28 Jan 2014 14:38:58 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o10.shared.sendgrid.net (o10.shared.sendgrid.net [173.193.132.135]) by neon.ruby-lang.org (Postfix) with SMTP id 7331E1204D0 for ; Tue, 28 Jan 2014 14:38:56 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=SYAdLOkMHhMl+ic3FM8GBQWCJbE=; b=tPcgdSU6CJZNIPEDnl 1ZZBkHBxpR3CFsHBr01wGWWtkX0r9LJyuiRN2HjUvKLNbxyWanhO4s6NqDHoAzH3 aY50BGDwCbtDU51f4tNM3dmNJbjOF20SHTtcIpdU+xjobVg462BKYlwZK9Hw2i6K r0Ctx0ycElNMotecp+IbgJXkk= Received: by mf196.sendgrid.net with SMTP id mf196.7178.52E7426E1 Tue, 28 Jan 2014 05:38:54 +0000 (UTC) Received: from herokuapp.com (ec2-54-196-94-22.compute-1.amazonaws.com [54.196.94.22]) by ismtpd-032 (SG) with ESMTP id 143d75b7e1b.1074.105c9f for ; Tue, 28 Jan 2014 05:38:54 +0000 (GMT) Date: Tue, 28 Jan 2014 05:38:53 +0000 From: davidm@astro.berkeley.edu To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 33913 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 9456 X-Redmine-Issue-Author: zzak X-Redmine-Issue-Assignee: aamine X-Redmine-Sender: david_macmahon X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: OOF Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS4dXxa4p+SNZxfL24GFjSiwfVhqYjU37L8S3DnQuaf9YDdUarfRCYTPxwTaQGo3r382JulVDba6sAroi+VtYEycKp2mgdUB4SYxlM+qZHUyIcVAlUQourtCNsa4kvhu7yQ= X-ML-Name: ruby-core X-Mail-Count: 60163 Subject: [ruby-core:60163] [ruby-trunk - Bug #9456] Include bin/racc with ruby 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: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #9456 has been updated by David MacMahon. I think a distinction needs to be made between the racc executable and the racc runtime library. My understanding is that the racc executable (bin/racc) is needed to develop a racc-based parser for a given application. Anyone who wants to use the application that contains the resultant parser needs the racc runtime library, but they don't need the racc executable. Thus, including the racc runtime library in the Ruby standard library is a way to ensure that racc parsers will be usable by anyone with a basic Ruby environment. Those who want to develop racc-based parsers will need the racc executable (and a suitable grammar file) to generate the parser, but those developers are more than capable of obtaining the racc executable (e.g. by installing the racc gem) for their own development environment. Instead of asking for bin/racc to be included in the standard library, it make more sense (IMHO) to ask whether the racc runtime could be removed from the standard library so as not to favor one parser runtime library over another one. For example, since the racc runtime is included in stdlib, why not also include the treetop runtime (if there is one) or any other "runtime" library in stdlib? Where does line of reasoning end? On the other hand, why even have a standard library if everything can be installed gems? Where would that line of reasoning end? My guess is that the racc runtime library has been "grandfathered in" since it has been part of stdlib for so long (since Ruby 1.6?). Dave On Jan 27, 2014, at 6:48 PM, e@zzak.io wrote: > Issue #9456 has been updated by Zachary Scott. > > >> Why gem is not enough? > > For the same reason that the gem is included in stdlib, if we can't include the full functionality of the gem then it shouldn't be inclued in stdlib. > > ---------------------------------------- > Bug #9456: Include bin/racc with ruby > https://bugs.ruby-lang.org/issues/9456#change-44648 > > * Author: Zachary Scott > * Status: Open > * Priority: Normal > * Assignee: Minero Aoki > * Category: > * Target version: current: 2.2.0 > * ruby -v: 2.2.0dev > * Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN > ---------------------------------------- > As you [can see](https://github.com/ruby/ruby/tree/trunk/bin) we include executables for Rake, RDoc, ri, ERB, RubyGems, and Irb with Ruby. > > We should also include Racc as an executable for Ruby. > > This resolves an issue where libraries requiring Racc, and using the binary executable, must install the Racc gem in order to use bin/racc. > > I'm fairly sure this change won't cause any issues, so I'd be happy to commit it. > > > > -- > http://bugs.ruby-lang.org/ ---------------------------------------- Bug #9456: Include bin/racc with ruby https://bugs.ruby-lang.org/issues/9456#change-44650 * Author: Zachary Scott * Status: Open * Priority: Normal * Assignee: Minero Aoki * Category: * Target version: current: 2.2.0 * ruby -v: 2.2.0dev * Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN ---------------------------------------- As you [can see](https://github.com/ruby/ruby/tree/trunk/bin) we include executables for Rake, RDoc, ri, ERB, RubyGems, and Irb with Ruby. We should also include Racc as an executable for Ruby. This resolves an issue where libraries requiring Racc, and using the binary executable, must install the Racc gem in order to use bin/racc. I'm fairly sure this change won't cause any issues, so I'd be happy to commit it. -- http://bugs.ruby-lang.org/