[#14696] Inconsistency in rescuability of "return" — Charles Oliver Nutter <charles.nutter@...>

Why can you not rescue return, break, etc when they are within

21 messages 2008/01/02
[#14699] Re: Inconsistency in rescuability of "return" — Gary Wright <gwtmp01@...> 2008/01/02

[#14738] Enumerable#zip Needs Love — James Gray <james@...>

The community has been building a Ruby 1.9 compatibility tip list on

15 messages 2008/01/03
[#14755] Re: Enumerable#zip Needs Love — Martin Duerst <duerst@...> 2008/01/04

Hello James,

[#14772] Manual Memory Management — Pramukta Kumar <prak@...>

I was thinking it would be nice to be able to free large objects at

36 messages 2008/01/04
[#14788] Re: Manual Memory Management — Marcin Raczkowski <mailing.mr@...> 2008/01/05

I would only like to add that RMgick for example provides free method to

[#14824] Re: Manual Memory Management — MenTaLguY <mental@...> 2008/01/07

On Sat, 5 Jan 2008 15:49:30 +0900, Marcin Raczkowski <mailing.mr@gmail.com> wrote:

[#14825] Re: Manual Memory Management — "Evan Weaver" <evan@...> 2008/01/07

Python supports 'del reference', which decrements the reference

[#14838] Re: Manual Memory Management — Marcin Raczkowski <mailing.mr@...> 2008/01/08

Evan Weaver wrote:

[#14911] Draft of some pages about encoding in Ruby 1.9 — Dave Thomas <dave@...>

Folks:

24 messages 2008/01/10

[#14976] nil encoding as synonym for binary encoding — David Flanagan <david@...>

The following just appeared in the ChangeLog

37 messages 2008/01/11
[#14977] Re: nil encoding as synonym for binary encoding — Yukihiro Matsumoto <matz@...> 2008/01/11

Hi,

[#14978] Re: nil encoding as synonym for binary encoding — Dave Thomas <dave@...> 2008/01/11

[#14979] Re: nil encoding as synonym for binary encoding — David Flanagan <david@...> 2008/01/11

Dave Thomas wrote:

[#14993] Re: nil encoding as synonym for binary encoding — Dave Thomas <dave@...> 2008/01/11

[#14980] Re: nil encoding as synonym for binary encoding — Gary Wright <gwtmp01@...> 2008/01/11

[#14981] Re: nil encoding as synonym for binary encoding — Yukihiro Matsumoto <matz@...> 2008/01/11

Hi,

[#14995] Re: nil encoding as synonym for binary encoding — David Flanagan <david@...> 2008/01/11

Yukihiro Matsumoto writes:

[#15050] how to "borrow" the RDoc::RubyParser and HTMLGenerator — Phlip <phlip2005@...>

Core Rubies:

17 messages 2008/01/13
[#15060] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Eric Hodel <drbrain@...7.net> 2008/01/14

On Jan 13, 2008, at 08:54 AM, Phlip wrote:

[#15062] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Phlip <phlip2005@...> 2008/01/14

Eric Hodel wrote:

[#15073] Re: how to "borrow" the RDoc::RubyParser and HTMLGenerator — Eric Hodel <drbrain@...7.net> 2008/01/14

On Jan 13, 2008, at 20:35 PM, Phlip wrote:

[#15185] Friendlier methods to compare two Time objects — "Jim Cropcho" <jim.cropcho@...>

Hello,

10 messages 2008/01/22

[#15194] Can large scale projects be successful implemented around a dynamic programming language? — Jordi <mumismo@...>

A good article I have found (may have been linked by slashdot, don't know)

8 messages 2008/01/24

[#15248] Symbol#empty? ? — "David A. Black" <dblack@...>

Hi --

24 messages 2008/01/28
[#15250] Re: Symbol#empty? ? — Yukihiro Matsumoto <matz@...> 2008/01/28

Hi,

Re: REXML::Element.write is deprecated. See REXML::Formatters

From: "Sean E. Russell" <ser@...>
Date: 2008-01-18 16:16:23 UTC
List: ruby-core #15135
On Wednesday 16 January 2008, Phlip wrote:
> > I guess I'll let Sean take it from here, other than to note that
> > .to_s on an element still works...
>
> I understand you only mean that's a workaround - it is indeed already
> deployed. But the complete rationale is useful here.

Your rationale, or mine?  

write() was deprecated because a large number of tickets were about 
pretty-printing: how it didn't do what people thought it would do, how 
it could be improved, and (as much as anything else) how the hell to 
use it.  The API was confusing and was only getting worse with age, and 
any attempt to make the formatting more "logical" for one person 
generated any number of complaints by other people.  The worst part, 
for me, was that formatting was adding significant bloat to the code.  
Ultimately, the right thing to do was to rip it out of the nodal 
classes and create its own infrastructure.

However, write() should still work; it *should* just call a default 
formatter to do the work.  That it doesn't is a bug.

As far as the missing Formatters class goes, any problems with REXML in 
the Ruby repository are my fault; ironically, Ruby moving to Subversion 
introduced some trouble on my end, as I had to start working with a new 
tool (svk) which (a) I discovered that I didn't like very much, and (b) 
my lack of knowledge about inevitably led to usage errors on my part.  
Consequently, it looks like the Formatters class didn't make it into 
the Ruby repository.

All of this should be fixed, assuming I don't make any more mistakes 
(don't hold your breath on that) with the next minor revision release 
this weekend.  Sam has been doing a huge amount of work with the 
repository, and I'm creating a point release just to propegate his 
fixes.  Hopefully, this will resolve your issues, and you should still 
be able to use to_s() and write().

In case I haven't been clear, for simple, dumb dumping of XML, with no 
promises about formatting, in the future you should use to_s().  This 
is the convenience method.  If you want control about how the XML is 
formatted, then use the Formatter API which -- I freely admit -- is 
poorly (if at all) documented.

> The goal of indent_xml() is to pretty-print tested XHTML so we can
> rapidly read it. It could have come from a human (icky formatting),

One benefit of the new Formatter API is that it is now vastly more easy 
to write your own formatters.

> or from some HTML generator (even ickier formatting!). And because
> HTML is not space-sensitive, the best solution is to format it as
> beautifully as possible, to help you see its structure and
> attributes.
>
> assert_xpath needs all this in its diagnostics, so you can rapidly
> see why an XPath was not found.

-- 
--- SER

Confidentiality Notice
This e-mail (including any attachments) is intended only for the recipients named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please notify the sender of that fact and delete the e-mail from your system.



In This Thread