hi fred,
this weekend i had time to take a look on the english forum and was very speechless by taking a clother look to the bug report section! there are a lot of some old and very old known posted bugs from 2002/2003 - and today in the year 2005 you reply that you have fixed the bugs now!?
laught or dont laugth? i feel me a bit like first april! isnt it really strange to get months/years later a fixed verison? what should interested newbies think about reading the topics?
would be interesting how do you think personaly about this and maybe you can give us all a possible statement why this happen so late? thanks
BUGS - be patienced for fixed versions?
Re: BUGS - be patienced for fixed versions?
> why this happen so late?
Like I said in another post: most bugs were not "show stoppers" and could
be fixed by some simple workarounds. What's the big deal in such cases?
Any major bugs are fixed very quickly.
Let's also put it into perspective: I own Visual Basic 5 Pro, and guess what?
I don't get ANY bug fixes or new features from Microsoft for that at all...
Like I said in another post: most bugs were not "show stoppers" and could
be fixed by some simple workarounds. What's the big deal in such cases?
Any major bugs are fixed very quickly.
Let's also put it into perspective: I own Visual Basic 5 Pro, and guess what?
I don't get ANY bug fixes or new features from Microsoft for that at all...
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
I had two possibilities while fixing bugs:
1) Doing the fix and delete the thread on the forum. The easy way.
2) Doing the fix and inform the community, even if it involve some criticizes. It seemed to be the most fair to do it as bug reporters took a lot of time to post good reports. BTW, the topics will be deleted once the new version will be released. About the lag about fix, you sometimes have other private issues which prevent you to do what you want in time.
1) Doing the fix and delete the thread on the forum. The easy way.
2) Doing the fix and inform the community, even if it involve some criticizes. It seemed to be the most fair to do it as bug reporters took a lot of time to post good reports. BTW, the topics will be deleted once the new version will be released. About the lag about fix, you sometimes have other private issues which prevent you to do what you want in time.
Fred - AlphaSND
-
freedimension
- Enthusiast
- Posts: 613
- Joined: Tue May 06, 2003 2:50 pm
- Location: Germany
- Contact:
I don't know, but from my point of view this is a very positive development. Fred is right now cleaning out all the bugs he had no time to fix back then. I guess that is because he has now much more time working for PureBasic. You know that he left his job to work on PB in fulltime just this year?
So, he is about to revise the whole language, to get a better basis for version 4.0
So, he is about to revise the whole language, to get a better basis for version 4.0
<°)))o><²³
> You will have to go and buy the new version [of VB]
Exactly my point. Ralf is onto a good thing with PureBasic and if some bug
fixes take a while, then he should be grateful he's getting them at all without
having to pay for them.
Exactly my point.
Ralf is onto a good thing with PureBasic and if some bugfixes take a while, then he should be grateful he's getting them at all without
having to pay for them.
I compile using 5.31 (x86) on Win 7 Ultimate (64-bit).
"PureBasic won't be object oriented, period" - Fred.
"PureBasic won't be object oriented, period" - Fred.
-
dracflamloc
- Addict
- Posts: 1648
- Joined: Mon Sep 20, 2004 3:52 pm
- Contact: