comp.lang.ada
 help / color / mirror / Atom feed
From: Brian May <bam@snoopy.apana.org.au>
Subject: Re: timeouts
Date: Fri, 27 Aug 2004 08:54:06 +1000
Date: 2004-08-27T08:54:06+10:00	[thread overview]
Message-ID: <sa4u0uph5o1.fsf@snoopy.apana.org.au> (raw)
In-Reply-To: mailman.8.1093523454.31213.comp.lang.ada@ada-france.org

>>>>> "Stephen" == Stephen Leake <stephen_leake@acm.org> writes:

    Stephen> Hmm. What other compiler (for any language) do you feel
    Stephen> has no bugs?

If I report a bug in the GCC C compiler, for example, then I can
access the fix as soon as it is applied to CVS (if I really want
it). There is also a publicly available list of bugs, so I can tell if
it really is a compiler bug or a bug in my code.

With GNAT, I do not get the fix when it is developed, but have to wait
until it is fixed in the free version.

According to another poster, this problem was known January 2003, that
is over one and a half years ago.

    Stephen> Personally, I don't trust _any_ compiler if I don't have
    Stephen> a support contract for it.

This might work for you, and it might work very well. It doesn't work
for everyone.

My understanding is that the support contracts are aimed at large
projects by large companies. If you are a small company, developing
software tools that don't contribute directly to company profits, then
a support contract may not be an option.

Even if I am wrong here, then a support contract is not really an
option when exclusively developing open source software.

Not that I have a problem with the business model that if you want the
newest features you have to pay for them, but I think an exception
needs to be made for bugs that cause valid code to fail in mysterious
ways.

If you want Ada to become popular, then it is necessarily for bug
fixes to be available to everyone too, including open source software
developers and companies that can't/won't pay for a support
contract. Otherwise that will just become yet another excuse for not
adopting Ada.

    Stephen> Again, what other compiler meets this criteria? GCC C,
    Stephen> maybe. _not_ GCC C++; I have lots of code that won't
    Stephen> compile. But C is not a very modern language, and I'll
    Stephen> take GNAT 3.15p over the latest GCC C compiler any day.

Also: With C or C++ you don't rely on the compiler so much to provide
high level objects. If, for instance, the package you relied on to
provide timers fails you can switch to another library.

In my case the solutions I have seen don't seem feasible:

* use Linux.

* purchase support contract. I have to convince the company that Ada
  is going to be more reliable first. I am not off to a good
  start. This isn't a major project that will generate heaps of
  income, rather its an expensive project (due to poor language choice
  by people who didn't understand its limitations) that everyone would
  prefer to forget about.

  It is very possible that I may be able to make this open source
  software too, so others can use it.

* use mingw compiler - I used that GNAT 3.14p compiler because it was
  my understanding it would be more reliable - has this changed now?

* use external library for timer stuff. Involves rewriting it.

* use another language. Involves rewriting it.
-- 
Brian May <bam@snoopy.apana.org.au>



  reply	other threads:[~2004-08-26 22:54 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 23:46 timeouts Brian May
2004-08-19  1:03 ` timeouts Jeffrey Carter
2004-08-19  3:10   ` timeouts Brian May
2004-08-19 19:18     ` timeouts Jeffrey Carter
2004-08-22  4:25       ` timeouts Brian May
2004-08-22 11:00         ` timeouts Stephen Leake
2004-08-22 11:29           ` timeouts Brian May
2004-08-22 19:56         ` timeouts Jeffrey Carter
2004-08-27 10:22           ` timeouts Brian May
2004-08-27 10:31             ` Cygwin and gcc-ada 3.4.1 (was Re: timeouts) Jano
2004-09-13 15:05               ` Dr Steve Sangwine
2004-08-27 17:54             ` timeouts Jeffrey Carter
2004-08-28  0:24             ` timeouts Stephen Leake
2004-08-29  0:24               ` timeouts Brian May
2004-08-29  4:40                 ` timeouts tmoran
2004-08-29  8:57                   ` timeouts Brian May
2004-08-29 17:17                     ` timeouts tmoran
2004-08-29 22:37                       ` timeouts Brian May
2004-08-29 13:31                 ` timeouts Stephen Leake
2004-08-29 22:32                   ` timeouts Brian May
2004-08-30  1:06                     ` timeouts Stephen Leake
2004-08-30 12:17                 ` timeouts Jano
2004-08-19  3:40 ` timeouts Steve
2004-08-22  4:18   ` timeouts Brian May
2004-08-22 12:54     ` timeouts Jeff C,
2004-08-26  1:28       ` timeouts Brian May
2004-08-26 10:00         ` timeouts Pascal Obry
2004-08-26 11:34           ` timeouts Georg Bauhaus
2004-08-26 11:58             ` timeouts Jean-Marc Bourguet
2004-08-26 22:20           ` timeouts Brian May
2004-08-27 18:12             ` timeouts Pascal Obry
2004-08-26 12:30         ` timeouts Stephen Leake
2004-08-26 22:54           ` Brian May [this message]
2004-08-27  1:17             ` timeouts Stephen Leake
2004-08-27  1:31             ` timeouts tmoran
2004-08-27  8:03               ` timeouts Brian May
2004-08-26 13:34         ` timeouts Steve
2004-08-26 14:02           ` timeouts Georg Bauhaus
2004-08-26 23:03             ` SPARK Brian May
2004-08-27 10:11               ` SPARK Georg Bauhaus
2004-08-26 23:20       ` timeouts Brian May
2004-08-27 10:20         ` timeouts Georg Bauhaus
2004-08-26 12:38   ` timeouts Jano
2004-08-26 19:07     ` timeouts Randy Brukardt
2004-08-26 21:25       ` timeouts tmoran
2004-08-26 23:01         ` timeouts Brian May
2004-08-27  0:03           ` timeouts Björn Persson
2004-08-27  9:31       ` timeouts Jano
2004-08-26 22:59     ` timeouts Brian May
2004-08-27  9:58       ` timeouts Jano
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox