[#6864] ruby 1.8.4 rc breaks alias_method/rails in bad ways — "Ara.T.Howard" <ara.t.howard@...>

20 messages 2005/12/09
[#6870] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — =?ISO-8859-15?Q?Florian_Gro=DF?= <florgro@...> 2005/12/12

Ara.T.Howard wrote:

[#6872] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, [ISO-8859-15] Florian Growrote:

[#6873] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — James Edward Gray II <james@...> 2005/12/12

On Dec 12, 2005, at 1:19 PM, ara.t.howard@noaa.gov wrote:

[#6874] Re: ruby 1.8.4 rc breaks alias_method/rails in bad ways — ara.t.howard@... 2005/12/12

On Tue, 13 Dec 2005, James Edward Gray II wrote:

[#6891] Time.utc! and Time.localtime! — Daniel Hobe <hobe@...>

Writing a script yesterday I found out, much to my surprise, that the

16 messages 2005/12/14

[#6918] change to yaml in 1.8.4 — ara.t.howard@...

14 messages 2005/12/16

[#6934] 1.8.x, YAML, and release management — Ryan Davis <ryand-ruby@...>

I'm concerned that 1.8.3's acceptance of non-backwards-compatible

28 messages 2005/12/18

[#6996] Problems building 1.8.4 with VS8 C++ Express Edition (cl 14.00) — Austin Ziegler <halostatue@...>

Visual Studio C++ 2005 Express Edition (VS 8.0)

20 messages 2005/12/27

Re: bug in mailread.rb, and: proposal for Mail#to_s

From: Wybo Dekker <wybo@...>
Date: 2005-12-07 09:51:52 UTC
List: ruby-core #6858
On Tue, 6 Dec 2005, daz wrote:

> Wybo Dekker wrote:
> 
> > On Tue, 6 Dec 2005, Yukihiro Matsumoto wrote:
> >
> > > I think to_s is not sufficient for string representation of whole mail
> > > body.  It's just too long.  I agreed to add a new method to do this
> > > work.  Any name suggestion?
> >
> >
> > [  # Return a Mail object, ready to print, [...]  ]
> 
>  def to_print
>     ...
>  end

this suggests that it's meant for printing. Actually, it is the reverse of 
what mailread does.
mailread reads the information of an e-mail message from an mbox file
into a Mail object.
The proposed method re-assembles this information into a string (perhaps
after editing it), ready be to written (back) to an mbox file. Hence my
proposal to name it to_s or assemble. 

How about to_mbox ?

Another point which should be considered is that mailread drops all
Receiver: fields except the last one. This is fine for me, but if I
were, for example, the developer of a mail reading application (like
pine or mutt) in Ruby, I wouldn't be happy with that... but maybe it's
considered stupid to do such developments in Ruby.

-- 
Wybo

In This Thread

Prev Next