From: "drbrain (Eric Hodel)" <drbrain@...7.net>
Date: 2013-08-22T04:55:47+09:00
Subject: [ruby-core:56776] [ruby-trunk - Feature #8807] Custom literals


Issue #8807 has been updated by drbrain (Eric Hodel).


If you define a new literal in file "a.rb" you cannot use it in that file that defined it as it has already been parsed. This may be confusing.
----------------------------------------
Feature #8807: Custom literals
https://bugs.ruby-lang.org/issues/8807#change-41318

Author: trans (Thomas Sawyer)
Status: Open
Priority: Normal
Assignee: 
Category: core
Target version: current: 2.1.0


So why can't we define custom literals? There's been recent discussion about adding a new freeze literal. Would have been nice if coders could have defined it for themselves, then it would have been more clear if there really was enough use to add it to core.

I imagine the syntax of such a feature to be quite simple.

  def %foo(string, mod=nil)
    p [string, mod]
  end

  %foo{something}o
  => ["something", "o"]




-- 
http://bugs.ruby-lang.org/