[#70977] [Ruby trunk - Feature #11473] Immutable String literal in Ruby 3 — arai@...
Issue #11473 has been updated by Shunichi Arai.
3 messages
2015/10/04
[#71062] [Ruby trunk - Bug #10892] Deadlock in autoload — eregontp@...
Issue #10892 has been updated by Benoit Daloze.
4 messages
2015/10/12
[#71090] Re: [Ruby trunk - Bug #10892] Deadlock in autoload
— Eric Wong <normalperson@...>
2015/10/14
eregontp@gmail.com wrote:
[#71127] [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call — normalperson@...
Issue #11607 has been updated by Eric Wong.
3 messages
2015/10/20
[#71164] [Ruby trunk - Feature #11614] [Open] [RFC] use id_table for constant tables — normalperson@...
Issue #11614 has been reported by Eric Wong.
3 messages
2015/10/22
[#71211] [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call — naruse@...
Issue #11607 has been updated by Yui NARUSE.
6 messages
2015/10/27
[#71212] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Eric Wong <normalperson@...>
2015/10/27
Yes, user must check if the function is MT-safe. Probably fine
[#71246] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Aaron Patterson <tenderlove@...>
2015/10/28
On Tue, Oct 27, 2015 at 08:54:07AM +0000, Eric Wong wrote:
[#71254] Re: [Ruby trunk - Feature #11607] [PATCH] fiddle: release GVL for ffi_call
— Eric Wong <normalperson@...>
2015/10/28
Aaron Patterson <tenderlove@ruby-lang.org> wrote:
[#71230] [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations — tenderlove@...
Issue #11625 has been updated by Aaron Patterson.
5 messages
2015/10/27
[#71236] Re: [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations
— Юрий Соколов <funny.falcon@...>
2015/10/28
What's about other hashsum algos? MD5, SHA2, etc
[#71242] Re: [Ruby trunk - Feature #11625] Unlock GVL for SHA1 calculations
— Eric Wong <normalperson@...>
2015/10/28
Юрий Соколов <funny.falcon@gmail.com> wrote:
[#71239] [Ruby trunk - Bug #11384] multi-threaded autoload sometimes fails — shugo@...
Issue #11384 has been updated by Shugo Maeda.
4 messages
2015/10/28
[ruby-core:71023] [Ruby trunk - Bug #11575] Blocks in ERB don't work as intended?
From:
rohitpaulk@...
Date:
2015-10-08 21:57:34 UTC
List:
ruby-core #71023
Issue #11575 has been updated by Rohit Kuruvilla.
Tried in on 1.8.7, same results. Is there a spec for eRuby somewhere that I can refer to?
----------------------------------------
Bug #11575: Blocks in ERB don't work as intended?
https://bugs.ruby-lang.org/issues/11575#change-54399
* Author: Rohit Kuruvilla
* Status: Open
* Priority: Normal
* Assignee:
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-darwin14]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
I'm not sure if this is a problem with ERB, but here it goes -
~~~
require 'ERB'
require 'Erubis'
$results = []
def return_block(&block)
result = block.call
$results << result
return result
end
erb_template = <<-ERB
<% return_block { %>
<% "This should be stored in $results, but not sent to output" %>
<% } %>
<% return_block { %>
<%= "This should be stored in $results AND sent to output" %>
<% } %>
ERB
puts "Result of Template is:"
puts "---------------------"
#puts Erubis::Eruby.new(erb_template).result
puts ERB.new(erb_template).result(binding)
puts "---------------------"
puts "First call to return_block: #{$results[0]}"
puts "Second call to return_block: #{$results[1]}"
~~~
I'd expect the output to be
~~~
Result of Template is:
---------------------
This should be stored in $results AND sent to output
---------------------
First call to return_block: This should be stored in $results, but not sent to output
Second call to return_block:
This should be stored in $results AND sent to output
~~~
And this is exactly what I get when using `Erubis`. When I use `ERB`, the output I get is -
~~~
Result of Template is:
---------------------
This should be stored in $results AND sent to output
---------------------
First call to return_block:
This should be stored in $results AND sent to output
Second call to return_block:
This should be stored in $results AND sent to output
~~~
I'm checking this against older ruby versions too, will update with results.
--
https://bugs.ruby-lang.org/