ruby-core

So, is it correct to assume that for language constructs that create built-in types like Range, Array, Hash etc that user-defined initialize methods are never called?

[#11549] Re: Proc initialize method not called under certain circumstances — "Berger, Daniel" <Daniel.Berger@...> 2007/06/28

> -----Original Message-----

[#11554] Re: Proc initialize method not called under certain circumstances — murphy <murphy@...> 2007/06/28

> ... for language constructs that create

[#11560] Re: Proc initialize method not called under certain circumstances — Yukihiro Matsumoto <matz@...> 2007/06/29

Hi,

[#11550] Re: Proc initialize method not called under certain circumstances — MenTaLguY <mental@...> 2007/06/28

On Fri, 29 Jun 2007 06:24:48 +0900, "John Lam (CLR)" <jflam@microsoft.com> wrote:

[#11553] Re: Proc initialize method not called under certain circumstances — "Marcel Molina Jr." <marcel@...> 2007/06/28

On Fri, Jun 29, 2007 at 06:54:49AM +0900, MenTaLguY wrote:

[#11548] NilClass, TrueClass, FalseClass special cased for singleton classes? — "John Lam (CLR)" <jflam@...>

If you do:

3 messages 2007/06/28

[#11557] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11559] Re: NilClass, TrueClass, FalseClass special cased for singleton classes? — Joel VanderWerf <vjoel@...> 2007/06/29

John Lam (CLR) wrote:

[#11555] Name of Classes — =?ISO-8859-15?Q?Wolfgang_N=E1dasi-Donner?= <wonado@...>

Moin, moin!

2 messages 2007/06/28

[#11558] Re: Name of Classes — Nobuyoshi Nakada <nobu@...> 2007/06/29

Moin,

[#11556] delete_if with destructive methods in block — Florian Gross <florgro@...>

Hi,

3 messages 2007/06/29

[#11561] Re: [BUG] delete_if with destructive methods in block — Nobuyoshi Nakada <nobu@...> 2007/06/29

Hi,

[#11567] Re: delete_if with destructive methods in block — Florian Gross <florgro@...> 2007/06/30

That fixes it for me. I got no regressions from Rubinius' hash spec

[#11562] Can clear frozen array using initialize() — Florian Gross <florgro@...>

Hi,

2 messages 2007/06/29

[#11563] Re: [BUG] Can clear frozen array using initialize() — Yukihiro Matsumoto <matz@...> 2007/06/30

Hi,

Re: Question about the patchlevel release cycle

From: "Sean E. Russell" <ser@...>

Date: 2007-06-21 03:35:47 UTC

List: ruby-core #11522

On Wednesday 20 June 2007 17:25, Michal Suchanek wrote:
> On 20/06/07, Alexey Verkhovsky <alexey.verkhovsky@gmail.com> wrote:
> > On 6/20/07, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:
...
> > As a downstream packager of sorts (http://rubyworks.thoughtworks.com),
> > I would be delighted, not annoyed, to receive a message every couple
> > of days (historical rate of patchlevel tags for 1.8.6) along the lines
> > of "hi, I've just tagged patchlevel X, it fixes bugs Y and Z".
> >
> > I realize that the same information could be obtained by watching the
> > 1_8_6 branch on Subversion, but that's extra digging for the knowledge
> > you have in your head when you tag a patchlevel.
>
> The commit messages should include that so it's only a matter of
> sending the commit messages to some sort of mailing list to which
> people could subscribe.

RSS or Atom feeds are also a nice way of getting this information, but 
somebody has to generate them.  If Ruby used Trac as it's bug tracking 
software, it would have RSS feeds automatically, but since it doesn't, there 
are a couple of ways to easily do this.

The ideal way requires the Subversion admins to set up a post-commit hook.  
Instructions are here:

http://www.friday.com/bbum/2006/08/17/howto-adding-an-rss-feed-to-a-subversion-server/

and the software is here:

http://svn.collab.net/repos/svn/trunk/tools/hook-scripts/svn2feed.py

Another way is to do the same thing with the post-commit hook, but rather than 
use a python script, run the mkatom.sh script in the tarball attached to this 
email (requires xsltproc) and expose the resulting feed.atom via HTTP.  It 
doesn't have to be a post-commit hook, but to be done externally, it'll have 
to be set up to poll.

In any case, post-commit hooks can do this all; I personally prefer a pull 
technology rather than yet another mailing list to maintain, but that's just 
a matter of preference.  It could be set up to spam people, too.

-- 
### SER   
### Deutsch|Esperanto|Francaise|Linux|XML|Java|Ruby|Haskell|Aikido|Iaido
### http://www.ser1.net, http://www.ser1.net/Security/ser_public.gpg
### Jabber: seanerussell@gmail.com (OTR enabled)

Attachments (1)

atom.tbz2 (5.48 KB, Archive)

Thread

Prev Next

In This Thread

Prev Next