[#1651] A min/max bug? — "Christoph" <chr_news@...>
Hi,
[#1690] Re: open-uri patch, added progress_proc hook — Elliott Hughes <ehughes@...>
In effect. I mean that if a method's interface is getting too complicated,
In article <AD4480A509455343AEFACCC231BA850F17C358@ukexchange>,
On Sun, Nov 16, 2003 at 07:51:42PM +0900, Tanaka Akira wrote:
[#1699] FileUtils bug and fix — Chad Fowler <chad@...>
As posted in ruby-talk:85349, I believe there is a bug in FileUtils.cp's
[#1706] gc_sweep in Ruby 1.8 — Richard Kilmer <rich@...>
I posted about this before but Matz wanted me to post more detail.
>>>>> "R" == Richard Kilmer <rich@infoether.com> writes:
[#1711] Re: open-uri patch, added progress_proc hook — "T. Onoma" <transami@...>
Tanaka Akira:
On Sunday 23 November 2003 07:12 pm, Mathieu Bouchard wrote:
On Sunday 23 November 2003 08:26 pm, Mathieu Bouchard wrote:
On Sunday 23 November 2003 09:32 pm, Mathieu Bouchard wrote:
On Sunday 23 November 2003 11:13 pm, Mathieu Bouchard wrote:
On Mon, Nov 24, 2003 at 05:32:09AM +0900, Mathieu Bouchard wrote:
[#1716] Re: open-uri patch, added progress_proc hook — "T. Onoma" <transami@...>
Tanaka Akira:
[#1718] Re: open-uri patch, added progress_proc hook — Elliott Hughes <ehughes@...>
In article <AD4480A509455343AEFACCC231BA850F17C434@ukexchange>,
On Saturday 22 November 2003 04:34 pm, Tanaka Akira wrote:
In article <200311221024.05642.transami@runbox.com>,
On Sunday 23 November 2003 02:24 am, Tanaka Akira wrote:
In article <200311230325.21687.transami@runbox.com>,
On Sunday 23 November 2003 03:10 pm, Tanaka Akira wrote:
In article <200311230648.41003.transami@runbox.com>,
On Monday 24 November 2003 03:19, Tanaka Akira wrote:
Sean E Russell [mailto:ser@germane-software.com] wrote:
[#1753] gc_sweep under 1.8 ... not syck.so — Richard Kilmer <rich@...>
We still encountered a gc_sweep in our use of Ruby 1.8 on Linux (v8).
>>>>> "R" == Richard Kilmer <rich@infoether.com> writes:
Yes, there are several (Ruby) threads working during this gc_sweep.
>>>>> "R" == Richard Kilmer <rich@infoether.com> writes:
of course this effects 300 machines ;-)
>>>>> "R" == Richard Kilmer <rich@infoether.com> writes:
The saga continues:
>>>>> "R" == Richard Kilmer <rich@infoether.com> writes:
There is a discussion (found by chad fowler) on ruby-dev (22000)
[#1755] Re: Controlled block variables — Jamis Buck <jgb3@...>
On Mon, 2003-11-24 at 02:04, T. Onoma wrote:
On Monday 24 November 2003 05:22 pm, Jamis Buck wrote:
On Monday 24 November 2003 11:51, T. Onoma wrote:
On Monday 24 November 2003 06:40 pm, Sean E Russell wrote:
On Tue, 25 Nov 2003, T. Onoma wrote:
On Monday 24 November 2003 14:02, T. Onoma wrote:
On Monday 24 November 2003 09:15 pm, Sean E Russell wrote:
[#1799] Syck install on Debian Standard (Ruby 1.6.7) — "T. Onoma" <transami@...>
Hi, I'm having some trouble installing Syck on Debain (woody). I'm not
On Friday 28 November 2003 09:17 am, T. Onoma wrote:
On Fri, Nov 28, 2003 at 05:22:48PM +0900, T. Onoma wrote:
[#1819] Re: configure.in: do not override CCDLDFLAGS, LDFLAGS, XLDFLAGS — Eric Sunshine <sunshine@...>
Hello,
Re: Controlled block variables
On Tuesday 25 November 2003 05:46 am, Dmitry V. Sabanin wrote:
> On Tuesday 25 November 2003 02:02, T. Onoma wrote:
> > No. Eval is for constructing code piecemeal with various variables, not
> > just to do what can already be done without it. But as it stands, one
> > must build literals within strings to accomplish such things. That's a
> > lot of extra work and makes for choppy ugly code.
>
> I think that eval just gives access to ruby interpreter itself in run-time.
> How could it behave differently from ruby then, if it _is_ ruby? That's
> just a needless ambiguity.
>
> > Of course, the above example dosen't really do what I want it to. For
> > that, I have to get fancy:
> >
> > p "#{a.join(',')}"
>
> You can just do p "#{a.inspect}", as it works great with strings, arrays
> and hashish..oops..hashes :). Or you always can define a method, i.e.
> to_evil in String, Array, Hash, or in any other class you use in eval, and
> use it like #{a.to_evil}.
> As I see it, it's just ten lines or so.
Hey! That's a workable solution. Not quite as clean, but it works for me.
Hmm...think i'll alias #i, or something small, for inspect. Nice.
> You can't change ruby behavior for things just to make it more comfortable
> for you, sometimes you have to change the way _you_ do it.
I wouldn't hold on to that argument too tightly, otherwise you might find
yourself programming in Assemby ;)
But if you mean JUST ME, then I wouldn't. I suggested it b/c I thought it
would be useful in general, and others might like to have it to. But your
solution in concise enough. So it's all good.
BTW: This idea first came out of my considering, "what-if" all blocks were
locally scoped-off, how would you get to variables outside? I thought of
"holes". With a notation like:
a = "hole"
{ "This is a block with a" + |a| + " in it." }
So when I was working with complex evals I kept thinking, "Ugh, I wish I had
that."
Thanks!
-t0