[#28687] [Bug #2973] rb_bug - Segmentation fault - error.c:213 — rudolf gavlas <redmine@...>

Bug #2973: rb_bug - Segmentation fault - error.c:213

10 messages 2010/03/16

[#28735] [Bug #2982] Ruby tries to link with both openssl and readline — Lucas Nussbaum <redmine@...>

Bug #2982: Ruby tries to link with both openssl and readline

16 messages 2010/03/18

[#28736] [Bug #2983] Ruby (GPLv2 only) tries to link to with readline (now GPLv3) — Lucas Nussbaum <redmine@...>

Bug #2983: Ruby (GPLv2 only) tries to link to with readline (now GPLv3)

10 messages 2010/03/18

[#28907] [Bug #3000] Open SSL Segfaults — Christian Höltje <redmine@...>

Bug #3000: Open SSL Segfaults

19 messages 2010/03/23

[#28924] [Bug #3005] Ruby core dump - [BUG] rb_sys_fail() - errno == 0 — Sebastian YEPES <redmine@...>

Bug #3005: Ruby core dump - [BUG] rb_sys_fail() - errno == 0

10 messages 2010/03/24

[#28954] [Feature #3010] slow require gems in ruby 1.9.1 — Miao Jiang <redmine@...>

Feature #3010: slow require gems in ruby 1.9.1

15 messages 2010/03/24

[#29179] [Bug #3071] Convert rubygems and rdoc to use psych — Aaron Patterson <redmine@...>

Bug #3071: Convert rubygems and rdoc to use psych

10 messages 2010/03/31

[ruby-core:29051] Re: [Feature #889] erb.rb should use Array and << for eoutvar and not String and concat

From: Jeremy Kemper <jeremy@...>
Date: 2010-03-26 20:30:00 UTC
List: ruby-core #29051
On Fri, Mar 26, 2010 at 11:45 AM, Kurt  Stephens <redmine@ruby-lang.org> wr=
ote:
> Issue #889 has been updated by Kurt =A0Stephens.
>
>
> This is not a good idea, because the expression value Strings accumulated=
 in the Array must be protected from mutation.
> ERB expressions can have side-effects.
>
> <pre>
> SOME_STRING =3D 'foobar'
> def foo
> =A0SOME_STRING
> end
> def bar
> =A0SOME_STRING.sub!(/bar/, '')
> =A0SOME_STRING
> end
> # ERB GENERATED CODE: from "<%=3D foo %><%=3D bar %>"
> eoutvar =3D [ ]
> eoutvar << foo
> eoutvar << bar
> eoutvar.join('')
> </pre>

I disagree. That's based on a loose assumption that <%=3D ... %> behaves
like #{...}.

But all it says is "output" not necessarily "interpolate" -- that's a
side effect of the current implementation. Much like using <% .... #
comment %> was an assumption that later broke.

jeremy

In This Thread