[#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: how to "borrow" the RDoc::RubyParser and HTMLGenerator

From: Phlip <phlip2005@...>
Date: 2008-01-19 03:39:53 UTC
List: ruby-core #15141
Eric Hodel wrote:

> This test has too many dependencies.  If your goal is to test 
> RDoc::Generator::HtmlMethod#markup_code, it shouldn't depend on the 
> parser's output.  It should construct the object whose method you're 
> going to test, and that's all.

I didn't know how to invoke the formatter without warming up every object that 
it depend on. The constructors seemed to require all those inputs.

> Is all this XML necessary?  I don't see any nested markup, and having to 
> figure out XPATH plus RDoc to add new tests seems like overkill.  
> Testing RDoc::Generator::HtmlMethod#markup_code directly without any 
> XML/XPATH will be much simpler and easier to understand by anyone who 
> wants to expand the tests.

Testing HTML via XPath is a best practice. As your HTML gets sicker, you can 
write sicker XPaths to match it. TDDers have been using XPath to test HTML since 
before Rails existed, for example. (I don't know about since before Ruby existed!;)

> That said, I'm really not sure what is being tested here.  The test's 
> class is RDocFormatTest, and there's a test_format method, but there's 
> no other mention of formats anywhere.  It appears to me you're testing 
> HTMLMethod#markup_code, but I could be wrong.  Maybe with all the 
> parsing stuff, you're really testing the parser?

Per the Subject line, I was researching how to set up the objects to convert 
arbitrary Ruby into its pretty-printed output. (And I am aware there are real 
pretty-printers out there.)

Does the code really need to write to a temporary file just to parse? Recall 
that's what the test_parse_c.rb does.

> If your test fails, where do I go to look for the problem?  It uses such 
> a large part of the RDoc library that it isn't going to help much in 
> tracking down bugs beyond "yes, it's broken".

In general, retrofitting developer tests to existing code requires an "any port 
in a storm" attitude, then running the tests after every few edits. That 
constrains the diagnosis to those last few edits.

When I began, if there had been two test cases, one showing how to parse, and 
the other formatting parsed tokens, then I don't think I would have had so much 
trouble doing my little experiment! Feel free to advise...

> Also, I find your use of 'muther luvvver' in poor taste.

Sorry - I try to restrict my Will Smith intake to less than an hour per month (-;

-- 
   Phlip


In This Thread