[#75225] [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7) — k@...
Issue #12324 has been reported by Kazuki Yamaguchi.
6 messages
2016/04/27
[#78693] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
k@rhe.jp wrote:
[#78701] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Kazuki Yamaguchi <k@...>
2016/12/17
On Sat, Dec 17, 2016 at 01:31:12AM +0000, Eric Wong wrote:
[#78702] Re: [Ruby trunk Feature#12324] Support OpenSSL 1.1.0 (and drop support for 0.9.6/0.9.7)
— Eric Wong <normalperson@...>
2016/12/17
Kazuki Yamaguchi <k@rhe.jp> wrote:
[ruby-core:74898] [Ruby trunk Feature#12272] Accepting HTML entity name in string literal
From:
shevegen@...
Date:
2016-04-12 15:00:37 UTC
List:
ruby-core #74898
Issue #12272 has been updated by Robert A. Heiler. I don't know. I am not really against it, also not really for it but to be honest, I can't remember either of these variants anyway. :) Would this actually be used/usable? ---------------------------------------- Feature #12272: Accepting HTML entity name in string literal https://bugs.ruby-lang.org/issues/12272#change-58024 * Author: Tsuyoshi Sawada * Status: Open * Priority: Normal * Assignee: ---------------------------------------- String literal allows the escape character `\u` to describe a character using UTF-8 character code like this: ~~~ruby "\u201c" # left double quote "\u2191" # up arrow ~~~ This is useful in typing characters that are not easy to input from the keyboard. However, normal people do not memorize the UTF-8 codes by heart. The HTML symbol entity name is the place where we can compromise (although it is not available for the entire UTF-8), I think. I would like the string literal to be extended to accept HTML entity names and interpret them as the corresponding UTF-8 characters. I do not have a definite idea for the syntax, but a candidate can be an escape character `\& ... ;`, so that we can type: ~~~ruby "\“" # left double quote "\↑" # up arrow ~~~ Currently, `"\&"` is interpreted as `"&"`, so this will be a compatibility breaking change, and if that is not desirable, perhaps a different syntax may be considered. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>