Bug fixed compiler claim disputedBy Chris Williams. Published: 9th May 2005, 00:11:53 | Permalink | Printable
Rewind that spin, say developersA developer has challenged Castle's claim that all bugs reported against its C/C++ compiler package have been fixed.
In an announcement issued on Wednesday regarding the release of version 5.6 of the Castle C/C++ development tools, Castle stated that "this new release includes fixes for all bugs reported through Castle's C support web pages". Over the weekend, freeware programmer Tom Hughes alleged that this was "an interesting but unfortunately blatantly untrue claim, or at the very least an exceedingly misleading one."
Tom continued: "I can't actually find any bug reporting mechanism mentioned on the Castle web site, so on that basis the claim may, strictly speaking, be true as no bugs can be reported via a mechanism that does not appear to exist."
Tom says he has sent Castle details of seven bugs plus one enhancement request, of which two were fixed in last week's 5.6 release. Yesterday, Castle's John Ballance contacted Tom to ask for his bug reports again, adding that he'll check to see if there is a link to the bug reporting system from the compiler tools website.
Tom told us that he wasn't overly upset at Castle, remarking: "I just don't like marketing people bending reality in their press releases." He claims he has found two bugs in build tool Amu, two minor faults in the linker and bogus warnings in the compiler, including a new erroneous warning generated by the 5.6 compiler.
It is possible that Tom is not alone: one developer told us that reporting bugs to Castle can, in his opinion, sometimes feel like sending email into a black hole. Another programmer commented: "Pity the poor debuggers if not only are they expected to beat their heads against the bugs but respond to the public as well, though I suppose somebody ought to be doing it."
John explained to us that developers can report bugs via email, using an address supplied with the compiler package. He said: "There has been, over time, a number of bugs reported [via email]. The reports do not always get an immediate response, but the bugs do get captured. Some bugs are 'user' issues, but as with any complex piece of software, some holes do get exposed. No compiler is released unless it passes many qualifying tests, which includes building successfully the Iyonix ROM. However, different code trees and coders can and do occasionally expose code sequences that cause issues.
"What the press release states is that, (to the best of my own knowledge) all bugs so far reported (by that mechanism) are resolved."
Previous: New ROS powered kit hinted
Next: R-Comp sneaks out VRPC graphics speed boost
DiscussionViewing threaded comments | View comments unthreaded, listed by date | Skip to the end
Please login before posting a comment. Use the form on the right to do so or create a free account.
Search the archives
Today's featured article
Adventures with a Lego-cased A7K web server
Having previously built desktop and laptop cases of out Lego bricks, model building Peter Howkins has turned his attentions towards crafting a slim box to slid his A7000 into a rack, alongside other rackmount servers. Having pieced together the housing, Peter puts a legacy RISC OS machine through its paces as an internet-facing server.
11 comments, latest by jess on 3/12/08 2:07PM. Published: 21 Nov 2008
Teking a little longer than expected
Artex's Tek is delayed a while
6 comments, latest by jmcarey on 18/4/02 1:49AM. Published: 16 Apr 2002
News and media:
RISCOS Ltd •
RISC OS Open •
MW Software •
Advantage Six •
CJE Micros •
Liquid Silicon •
Chris Why's Acorn/RISC OS collection •
The Register •
The Inquirer •
Apple Insider •
BBC News •
Sky News •
Google News •