From: Xavier Noria <fxn@...>
Date: 2012-04-23T22:55:56+09:00
Subject: Re: gem-packed script with DATA section does not work

--047d7b15a61f38764104be58ff6d
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 23, 2012 at 1:49 PM, Wybo Dekker <wybo@xs4all.nl> wrote:

That's clear, but does that mean there's no workaround?
> Can Ruby not be told that the DATA section is somewhere else?
>

There's no workaround related to the DATA constant itself, it's defined
only for the main file.

You could of course switch to regular Ruby, for example throwing at the end
of the script:

    BEGIN {
      require 'stringio'
      DATA = StringIO.new(<<EOS)
      ...
      EOS
    }

That'd work because the main file is not going to define DATA (RubyGems
does not generate __END__), so the constant is undefined. You could also
scan __FILE__ in a BEGIN block looking for __END__ by hand to fully emulate
the feature.

The BEGIN block is needed because in the original DATA feature you get the
constant defined in the top-level right away if __END__ is present.

Well just giving some ideas, the main point is that you need to do it in
Ruby.

--047d7b15a61f38764104be58ff6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_extra">On Mon, Apr 23, 2012 at 1:49 PM, Wybo Dekker <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:wybo@xs4all.nl" target=3D"_blank">wybo=
@xs4all.nl</a>&gt;</span> wrote:</div><div class=3D"gmail_extra"><br></div>=
<div class=3D"gmail_extra">



<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That&#39;s clear,=
 but does that mean there&#39;s no workaround?<br>
Can Ruby not be told that the DATA section is somewhere else?<br></blockquo=
te><div><br></div><div>There&#39;s no workaround related to the DATA consta=
nt itself, it&#39;s defined only for the main file.</div><div><br></div>


<div>You could of course switch to regular Ruby, for example throwing at th=
e end of the script:</div><div><br></div><div><div>=C2=A0 =C2=A0 BEGIN {</d=
iv><div>=C2=A0 =C2=A0 =C2=A0 require &#39;stringio&#39;</div><div>=C2=A0 =
=C2=A0 =C2=A0 DATA =3D StringIO.new(&lt;&lt;EOS)</div>


<div>=C2=A0 =C2=A0 =C2=A0 ...</div><div>=C2=A0 =C2=A0 =C2=A0 EOS</div><div>=
=C2=A0 =C2=A0 }</div></div><div><br></div><div>That&#39;d work because the =
main file is not going to define DATA (RubyGems does not generate __END__),=
 so the constant is undefined. You could also scan __FILE__ in a BEGIN bloc=
k looking for __END__ by hand to fully emulate the feature.</div>

<div><br></div><div>The BEGIN block is needed because in the original DATA =
feature you get the constant defined in the top-level right away if __END__=
 is present.</div>
<div><br></div><div>Well just giving some ideas, the main point is that you=
 need to do it in Ruby.</div><div><br></div></div></div>

--047d7b15a61f38764104be58ff6d--