That strange, developers team do nothing without ready sample. See http://www.freepascal.org/mantis/view.php?id=10457

Andrey Gusev wrote

That strange, developers team do nothing without ready sample. See http://www.freepascal.org/mantis/view.php?id=10457

First of all, it is not correct that they 'do nothing'.

Fixing a bug for which there is no test code is very hard. There are 280.000 lines of code in the compiler.

With simple and straightforward code, the bug is not reproducible. I have tried this.

So, yes, you must provide an example so the bug can be located within a more reasonable amount of time.

There is nothing wrong with asking that, I think ?

Michael.

* Michael Van Canneyt [Sat, 22 Dec 2007
00:43:37 +0100 (CET)]:

I have regarded the #16839 raply and switching state to "information" as direct refusal to do wasn't right ?

Fixing a bug for which there is no test code is very hard. There are 280.000 lines of code in the compiler.

I also now have under lazarus/fpc ~100000 lines of my sources (on me one),
so question in that, for whom is more harder to investigate YOUR errors ?
Apparently, i must accept as my duty only differential diagnostic between your and my code.
I think, on stage of publishing (cutted) DM1.pas in #10457 report my duties was ended.
The rest has been done only from my LOVE to fpc and lazarus (that error was not critical to my projects).
I expected more activity from developers team in serious errors investigation.

With simple and straightforward code, the bug is not reproducible. I have tried this. So, yes, you must provide an example so the bug can be located within a more reasonable amount of time.

DM1.pas part published have all required to error localization. {$mode delphi} significance clarification has taken away ~20 minutes of time.
But that even not was tried, it may be guilty New Year's holidays ?

There is nothing wrong with asking that, I think ?

Nothing, but I have regarded it as the requirement.

I do not try at all start squabble, i'm possible is simply tired.

Andrey Gusev wrote

I expected more activity from developers team in serious errors investigation.

Huh? You are talking to people who develop FPC for free, who have to go to work every day to pay their bills and who also have a family life. But you "expect more activity from them"?

As a FPC user, I prefer they spend their time in developping FPC, not in searching bugs that, maybe, exist nowhere but in a user program. Of course, it is up to us, FPC users, to provide the code that activates a bug.

mm
http://www.ellipsa.net/

Apparently, i must accept as my duty only differential diagnostic between your and my code.

Yes, less or more :) That's the price for using OSS, see also the link below.

I think, on stage of publishing (cutted) DM1.pas in #10457 report my duties was ended. The rest has been done only from my LOVE to fpc and lazarus (that error was not critical to my projects).

Guess what drives fpc and lazarus development?

I expected more activity from developers team in serious errors investigation.

<http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/>

No, it is the start of the bug-solving process.

The information you provided was not enough to start solving the bug, so we ask for more information. That is why the 'information' or 'feedback' state exists in Mantis.

If we won't fix something, you will see the state "won't fix".

Michael.

OK, subject is closed.

I have been angry on Friday, about 20 reports to LazReport should be transformed (by hands, as i undestanded)...
And here still these errors (codepages in LazReport is critical to my projects)...

Thanks:
to Michael Van Canneyt for explanations about error tracking process - it is useful to me
to Florian Klaempfl for respond, the cathedral-bazaar is known to me a long time, probably I already have had time to forget it to "mm" for the drawn terrible picture of programmers existence outside of my near environment

Excuse me, if I have told something insulting or rough (though i am assured that all told by me was absolutely correctly and politely, only I am not completely confident the my English).

A.G.