Shareaza

I have no "beta testing" and no devs working on DC++ at all.

What does all of that mean? Surely it doesn't mean you're going to take that list of several specific bugs and ignore it and not fix any of them?

Its not a bug just unimplemented functionality.

What is "not a bug"? Search results appearing in the wrong search tabs is a bug. (In fact they're sometimes appearing in multiple tabs -- I've had a single result appear duplicated among five out of six active tabs.) Downloads not being verified, at least after completion by comparing the downloaded file's hash with the search result's hash if nothing better such as TigerTree was available for that file, is a bug. Handshaking freezing at "Requesting" and failing to either progress or time out (even after hours!) is a bug. Resuming of downloads invariably corrupting them is a bug. Misinterpreting busy signals as permanent fatal errors is a bug. Downloads.NeverDrop not performing as advertised is a bug. And last but certainly not least crashes are bugs.

So would you mind telling me what, precisely, you were saying was not a bug?

What ryo is saying that despite 2.5.4.0 being a "stable" release version, the DC++ included is in fact in alpha stage, it is not feature complete or tested to be stable. You should not and cannot assume that it will work correctly. The reason it doesn't is not due to fixable programming errors, aka "bugs", it is because it simply is incomplete. I assume it is included with the "stable" release because neither removing it from the code nor waiting until it is completed was practical. And maybe ryo assumed nobody was interested in it and would go thru the bother of getting it run anyway?

Just my interpretation, though. Did I get it right?

Speaking of Tim he has a very distinctive way of writing and expressing himself. Kind of makes me wonder how on Earth he manages to use multiple user accounts to establish multiple supporting personae on forums which he mentioned to me has become something of necessity in forums due to all the people who attack him without reason. I probably should ask him but I kind of promised not to bother tharrison1 again.

@blackflag100:
Since you seem to have similar opinions as tharrison1 would you like me to add you to my ignore list as well? You don't seem to get anything useful from my posts anyway...

If you do not help us finding the bug, then we can't fix it. It's as simple as that.

Also I don't think it ever was really established it was the debugging code as such that caused the freeze, just that it was much worse in debug builds. (IIRC?) The difference being that if the actual root cause has been fixed or it was triggered by some condition that no longer exists, the debug build might now work just fine. (Worth checking maybe?) They do for most people, you know. No supercomputers required either. My previous computer was an AthlonXP and it ran debug builds just fine.

Its by design. Since search hits for DC++ and eD2K has no ID (due protocol limitation), hits goes to every opened search tab to show full map of results. There is no reason to show hit in one search but not in second.

1. nop
2. nop
3. nop
4. nop
5. nop

P.S. please relax

Why not?