[antlr-interest] Serious Bug when using BitSetgeneration

Tue Nov 22 07:06:56 PST 2005

And YOU aren't paying the ANTLR team either.

Maybe if you were, you'd carry more weight when you try to call the
shots.

Cheers,
Wol

-----Original Message-----
From: antlr-interest-bounces at antlr.org
[mailto:antlr-interest-bounces at antlr.org] On Behalf Of Geir Ove
Skjaervik
Sent: 18 November 2005 21:15
To: 'ANTLR Interest'
Subject: RE: [antlr-interest] Serious Bug when using BitSetgeneration

Hello,

Obviosuly you haven't read my previous postings on this: I have said
that I will post an example of the problem WHEN I am able to produce a
small case that shows the problem and WHEN I have the time for it on my
project: My clients are NOT paying me to post bug reports to you. Surely
you know how that works.

Who said I am taking the ANTLR team for gratnted ? As a matter of fact,
I have on several occasions thanked Terrence for bringing this great
tool to the community.

However, none of this fixes the bug. It is wasted bandwith on this
forum.

Geir Ove

-----Original Message-----
From: Akhilesh Mritunjai [mailto:virtualaspirin at yahoo.com] 
Sent: 18. november 2005 21:30
To: Geir Ove Skjaervik; 'ANTLR Interest'
Subject: RE: [antlr-interest] Serious Bug when using BitSetgeneration

Geir

I've been using ANTLR a bit longer than you, and my
perception is different.

If you're a developer with any significant experience
I'd expect you to know the basics of QA process.

While logging a bug one is supposed to give
description of the problem with a test case in which
bug is at least sometimes reproducible.

This has been iterated again and again, many people
think it is an interesting and priority bug, *if* it
infact exists. So far you have not provided any inputs
to demonstrate it is there!

Understand that its hard to look for a something if
you dont even know how it looks like or if its infact
there.

Oh, and taking people who work for nothing and provide
a tool of this quality, for granted, *is NOT polite*.
If you can't invest time to come up with a testcase
how do you expect people to spend their time hunting
down something that may or may not be there just
because someone sent a feedback 'hey I think its
there!'

- Akhilesh

--- Geir Ove Skjaervik <geiroves at online.no> wrote:

> Hello,
> 
> Are we supposed to take this kind of feedback
> seriously? You may make
> fun of other peoples problems, but does this kind of
> feedback belong
> here?
> 
> You clearly do not understand the nature of the
> problem, or you would
> not have replied the way you do; and when you do not udnerstand, why
> don't you refreain from replying?
> 
> a) Switching to 3.x is NOT an option after having
> written about 5000
> lines of Parser and Tree Parser code
> 
> b) If it is a limitation, ANTLR should warn you
> about that.
> 
> c) The workaround means avoiding BitSets alltogehter
> for ** everyone **.
> As long as we (programmers and the ANTLR developemnt
> team) does NOT
> understand the nature of the problem, then we do NOT
> know when this bug
> strikes!
> 
> d) Avoiding BitSets all the time means two things: 
>    i) Performance takes a big hit
>    ii) Why are they there if all they can do is pose
> a BIG problem in
> unknown situations
> 
> 
> 
> 
> Geir Ove
> 
> 
> Geir Ove
> 
> -----Original Message-----
> From: antlr-interest-bounces at antlr.org 
> [mailto:antlr-interest-bounces at antlr.org] On Behalf Of Jim Idle
> Sent: 18. november 2005 04:24
> To: ANTLR Interest
> Subject: RE: [antlr-interest] Serious Bug when using
> BitSetgeneration
> 
> 
>  
> 
> ________________________________
> 
> From: antlr-interest-bounces at antlr.org on behalf of
> Geir Ove Skjaervik
> 
> 
> Jim Idle wrote:
> 
> > Hello,
> 
> > Just one more comment on this Bug. It is **
> clearly ** a bug, since
> > ANTLR does work correctly when BitSets are NOT
> used.
> 
> Well, it could be just a limitation, perhaps catered
> for with a few
> tweaks, or perhaps better addressed with efforts in
> the Antlr 3 space.
> 
> >I find it strange
> > that this Bug  seems to be passed in almost
> silence: I would think it
> >to  be rather serious to have a "sleeping" bug that
> may come and bite
> >you  any time you encounter the right conditions.
> 
> > Terrence asked me to try to produce a small
> grammar example to try to
> > reproduce the problem. I will as soon as time on
> my project permits
> > it.
> 
> Hmmm - I thought you said it was a serious bug?
> Can't be THAT serious
> can it? ;-)
> 
> > BUT I would think it is equally IMPORTANT for the
> ANTLR team to try to
> 
> > hunt down this ** serious ** bug. It is nice that
> ANTLR 3.0 is under
> > development, but we sure need a strong ** core **
> technology that
> > won't fail.
> 
> Well, the last time I was there I noticed that beer
> and pizza were
> significantly more expensive in San Francsico than
> most other parts of
> the world except Geneva. I am sure that donating a
> few vouchers for same
> would make this bug very much more important.
> Remember that it is free
> (for you anyway) and we should be careful to give
> out a bit of respect
> for people's time and efforts given freely :-).
> 
> Jim
> 
> 
> 
> 

__________________________________ 
Yahoo! FareChase: Search multiple travel sites in one click.
http://farechase.yahoo.com

* ************************************************************************ *

This transmission is intended for the named recipient only. It may contain private and confidential information. If this has come to you in error you must not act on anything disclosed in it, nor must you copy it, modify it, disseminate it in any way, or show it to anyone. Please e-mail the sender to inform us of the transmission error or telephone ECA International immediately and delete the e-mail from your information system.

Telephone numbers for ECA International offices are: Sydney +61 (0)2 8272 5300, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 212 582 2333.

* ************************************************************************ *