[#7271] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7272] [PATCH] OS X core dumps when $0 is changed and then loads shared libraries — noreply@...
Bugs item #3399, was opened at 2006-01-31 22:25
[#7274] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7277] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7280] Re: [PATCH] solaris 10 isinf and ruby_setenv fixes — ville.mattila@...
[#7286] Re: ruby-dev summary 28206-28273 — ara.t.howard@...
On Thu, 2 Feb 2006, Minero Aoki wrote:
mathew wrote:
mathew wrote:
I'm not sure we even need the 'with' syntax. Even if we do, it breaks
On 2006.02.07 10:03, Evan Webb wrote:
Umm, on what version are you seeing a warning there? I don't and never
On 2006.02.07 14:47, Evan Webb wrote:
I'd by far prefer it never emit a warning. The warning is assumes you
On Tue, 7 Feb 2006, Evan Webb wrote:
On Wed, 8 Feb 2006, Timothy J. Wood wrote:
[#7305] Re: Problem with weak references on OS X 10.3 — Mauricio Fernandez <mfp@...>
On Sun, Feb 05, 2006 at 08:33:40PM +0900, Christian Neukirchen wrote:
On Feb 5, 2006, at 5:05 AM, Mauricio Fernandez wrote:
On Wed, Feb 22, 2006 at 02:21:24PM +0900, Eric Hodel wrote:
Hi,
On Mon, Feb 27, 2006 at 12:45:28AM +0900, Yukihiro Matsumoto wrote:
On Sun, Feb 26, 2006 at 06:06:17PM +0100, Mauricio Fernandez wrote:
In article <20060226171117.GB29508@tux-chan>,
In article <1140968746.321377.18843.nullmailer@x31.priv.netlab.jp>,
Hi,
In article <m1FDshr-0006MNC@Knoppix>,
In article <87irr047sx.fsf@m17n.org>,
In article <87vev0hxu5.fsf@m17n.org>,
Just my quick 2 cents...
In article <92f5f81d0602281855g27e78f4eua8bf20e0b8e47b68@mail.gmail.com>,
Hi,
In article <m1FESAD-0001blC@Knoppix>,
Hi,
[#7331] Set containing duplicates — noreply@...
Bugs item #3506, was opened at 2006-02-08 22:52
[#7337] Parse error within Regexp — Bertram Scharpf <lists@...>
Hi,
Hi,
On Sun, Feb 12, 2006 at 01:34:55AM +0900, Yukihiro Matsumoto wrote:
[#7344] Ruby 1.8.4 on Mac OS X 10.4 Intel — Dae San Hwang <daesan@...>
Hi, all. This is my first time posting to this mailing list.
On Feb 12, 2006, at 6:14 AM, Dae San Hwang wrote:
[#7347] Latest change to eval.c — Kent Sibilev <ksruby@...>
It seems that the latest change to eval.c (1.616.2.154) has broken irb.
Hi,
Thanks, Matz.
[#7364] Method object used as Object#instance_eval block doesn't work (as expected) — noreply@...
Bugs item #3565, was opened at 2006-02-15 02:32
Hi,
Hi,
On Pr 2006-02-16 at 03:18 +0900, Yukihiro Matsumoto wrote:
[#7376] Minor tracer.rb patch — Daniel Berger <Daniel.Berger@...>
Hi,
[#7396] IO#reopen — Mathieu Bouchard <matju@...>
[#7403] Module#define_method "send hack" fails with Ruby 1.9 — Emiel van de Laar <emiel@...>
Hi List,
Emiel van de Laar <emiel@rednode.nl> writes:
Hi --
[#7439] FYI: ruby-lang.org is on spamcop blacklists — mathew <meta@...>
dnsbl/bl.spamcop.net returned deny: for
[#7442] GC Question — zdennis <zdennis@...>
I have been posting to the ruby-talk mailing list about ruby memory and GC, and I think it's ready
Hello.
Hello.
Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273)
Umm, on what version are you seeing a warning there? I don't and never
have gotten a warning doing that exact thing.
- Evan
On 2/6/06, Eero Saynatkari <ruby-ml@magical-cat.org> wrote:
> On 2006.02.07 10:03, Evan Webb wrote:
> > I'm not sure we even need the 'with' syntax. Even if we do, it breaks
> > the programmers context in a way that we might not want to have to
> > explain constantly. I can just hear the questions now...
> >
> > "Why are my method calls inside a with being executed on the wrong object?"
> >
> > "Well, thats because with changes self for it's body, and so you have
> > to be careful what you call in there."
> >
> > repeat..
> >
> > While the more hardcore of us are use to using blocks to enter into
> > new and strange contexts (module_eval/class_eval/instance_eval oh
> > my!), pushing this to the normal user is not a decision that should be
> > made lightly.
> >
> > As for the original syntax "&?" I'm against it. It adds a significant
> > new level of unreadability. At this stage of the game, any syntax
> > changes need to really thought out. We've already got a great,
> > expressive syntax. If you want to do away with the duplication of
> > effort, use a local variable, thats what there there for:
> >
> > if t = a[0] and t.strip.empty?
> > # jump off a bridge
> > end
> >
> > On a regular basis I write:
> >
> > if a = something_long
> > a.another_operation
> > end
> >
> > The local variable a gets the value "cached" and then we get to do a
> > conditional on it's value right away. We've got a language where
> > everything is an expression, lets use it!
>
> A minor nitpick, you need
>
> if (t = something.first) and t.strip.empty?
> # ...
> end
>
> Otherwise a warning will be emitted (sensible behaviour).
>
> > - Evan
> >
> > On 2/3/06, James Britt <ruby@jamesbritt.com> wrote:
> > > mathew wrote:
> > > >...
> > >
> > >
> > > > with a[1]
> > > > strip!
> > > > empty?
> > > > end
> > > >
> > > > or similar. Hopefully you get the basic idea anyway, and someone can
> > > > refine the semantics if they like it...
> > >
> > >
> > > I'm not too keen on terse syntax; clarity for the read takes precedence
> > > over ease for the writer. The 'with' syntax is more expressive.
> > >
> > >
> > > James
> > >
> > >
> > >
> >
> >
> > --
> > When I do good, I feel good; when I do bad, I feel bad,
> > and that is my religion.
> > -- Abraham Lincoln (1809 - 1865)
>
>
> E
>
>
--
When I do good, I feel good; when I do bad, I feel bad,
and that is my religion.
-- Abraham Lincoln (1809 - 1865)