Reporting Bugs about REXML?

ruby-talk
1

Hi,

where would I report a bug about ruby REXML?

I did not yet find a proper way to report any bug. Starting at
ruby-lang.org I came to redmine.org and registered, but then I just
get an empty list of issues assigned to me and another empty list of
issues, but no way to enter a new issue.

Is there any bug tracking for ruby ?

regards
Hadmut

2

Hi,

where would I report a bug about ruby REXML?

I did not yet find a proper way to report any bug. Starting at
ruby-lang.org I came to redmine.org and registered, but then I just
get an empty list of issues assigned to me and another empty list of
issues, but no way to enter a new issue.

Hmm IIRC that would be on ruby-core

HTH
R.

···

On Fri, May 14, 2010 at 4:07 PM, Hadmut Danisch <hadmut@danisch.de> wrote:

Is there any bug tracking for ruby ?

regards
Hadmut

--
The best way to predict the future is to invent it.
-- Alan Kay

3

Just FYI, REXML is probably the worst possible XML library available
for Ruby so I wouldn't waste my time with it if I were you. There are
lots of better alternatives out there, including libxml-ruby and
Nokogiri.

Michael

···

--
Michael Jackson

@mjijackson

On Fri, May 14, 2010 at 8:07 AM, Hadmut Danisch <hadmut@danisch.de> wrote:

Hi,

where would I report a bug about ruby REXML?

I did not yet find a proper way to report any bug. Starting at
ruby-lang.org I came to redmine.org and registered, but then I just
get an empty list of issues assigned to me and another empty list of
issues, but no way to enter a new issue.

Is there any bug tracking for ruby ?

regards
Hadmut

4

I recently have asked a question about the standard library on
ruby-core and was told that this is not what ruby-core is for...

regards
Hadmut

···

On Sat, May 15, 2010 at 01:05:34AM +0900, Robert Dober wrote:

>
Hmm IIRC that would be on ruby-core

5

Just FYI, REXML is probably the worst possible XML library available
for Ruby so I wouldn't waste my time with it if I were you. There are
lots of better alternatives out there, including libxml-ruby and
Nokogiri.

This blog post might be relevant to your interest:

http://blog.directededge.com/2010/05/06/making-activeresource-34x-faster-qactiveresource/
I know this isn't a rails mailing list, but if speed is of utmost important,
this might not be a bad route.

Andrew McElroy

···

On Fri, May 14, 2010 at 5:55 PM, Michael Jackson <mjijackson@gmail.com>wrote:

Michael

--
Michael Jackson
http://mjijackson.com
@mjijackson

On Fri, May 14, 2010 at 8:07 AM, Hadmut Danisch <hadmut@danisch.de> wrote:
> Hi,
>
> where would I report a bug about ruby REXML?
>
>
> I did not yet find a proper way to report any bug. Starting at
> ruby-lang.org I came to redmine.org and registered, but then I just
> get an empty list of issues assigned to me and another empty list of
> issues, but no way to enter a new issue.
>
>
> Is there any bug tracking for ruby ?
>
>
> regards
> Hadmut
>
>

6

Well, I feel a little bit annoyed about such recommendations like
"don't use what comes with ruby, get some much better stuff from xyz",
I'll expect ruby to come with working stuff.

The documentation of the libxml-ruby of current ubuntu (generated with
rdoc) is poor. Sometimes it referes to empty pages.

And something like

dc = xml.find("/document-content")

dc.each do |node|
  puts "Node #{node}"
end

does not find anything either.

regards
Hadmut

···

On Sat, May 15, 2010 at 07:55:44AM +0900, Michael Jackson wrote:

Just FYI, REXML is probably the worst possible XML library available
for Ruby so I wouldn't waste my time with it if I were you. There are
lots of better alternatives out there, including libxml-ruby and
Nokogiri.

7

If you have a bug, not a question about how to use the standard library,
ruby-core is the correct mailing list.

···

On Sat, May 15, 2010 at 02:08:01AM +0900, Hadmut Danisch wrote:

On Sat, May 15, 2010 at 01:05:34AM +0900, Robert Dober wrote:
> >
> Hmm IIRC that would be on ruby-core

I recently have asked a question about the standard library on
ruby-core and was told that this is not what ruby-core is for...

--
Aaron Patterson
http://tenderlovemaking.com/

8

Well, I feel a little bit annoyed about such recommendations like
"don't use what comes with ruby, get some much better stuff from xyz",

Ruby is a wonderful programming language, but should that not be a
reason not to have wonderful extensions and/or bindings.
It is completely normal that bindings to high class libraries as xml
will beat built in stuff like REXML.
I am sure that we all pointed out here is meaning if by any means
REXML does not do your job, no worries there are other solutions.
Maybe that was not clear.

I'll expect ruby to come with working stuff.

So do I and AAMOF Ruby complies. And sorry for insisting but REXML is
not broken, just limited, mainly in performance.

The documentation of the libxml-ruby of current ubuntu (generated with
rdoc) is poor. Sometimes it referes to empty pages.

And something like

dc = xml.find("/document-content")

dc.each do |node|
puts "Node #{node}"
end

does not find anything either.

If you provided the document one might be able to help.

Cheers
Robert

···

On Sun, May 23, 2010 at 10:02 AM, Hadmut Danisch <hadmut@danisch.de> wrote:

--
The best way to predict the future is to invent it.
-- Alan Kay

9

Just FYI, REXML is probably the worst possible XML library available
for Ruby so I wouldn't waste my time with it if I were you. There are
lots of better alternatives out there, including libxml-ruby and
Nokogiri.

Well, I feel a little bit annoyed about such recommendations like
"don't use what comes with ruby, get some much better stuff from xyz",
I'll expect ruby to come with working stuff.

I don't agree to that assessment of Michael. Whenever I have to deal
with XML in Ruby REXML is my first choice and it has worked out
remarkably well (if you ignore performance).

The documentation of the libxml-ruby of current ubuntu (generated with
rdoc) is poor. Sometimes it referes to empty pages.

And something like

dc = xml.find("/document-content")

IIRC XPath notation this will only find element "document-content" at
root level. You probably rather want "//document-content".

dc.each do |node|
puts "Node #{node}"
end

does not find anything either.

I second Robert, please show the document and probably a bit more code.

Kind regards

robert

···

2010/5/23 Hadmut Danisch <hadmut@danisch.de>:

On Sat, May 15, 2010 at 07:55:44AM +0900, Michael Jackson wrote:

--
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/