G
goose
Mark McIntyre said:Support. Lots of people spend lots of money for compilers that don't
outperform GCC just so they have someone to complain to and, if
necessary, sue when there are problems.
And before anyone says "but GCC has a huge support team" remember that
none of them are paid to do it, and, unlike your contracted commercial
supplier, can walk away if they don't fancy fixing the bug.[/QUOTE]
sadly, the commercial support is so bad (here in SA, anyway) that i'd rather
stuff my eyeballs into my ears than listen to why the problem is not
theirs but mine, and to use this 'workaround' ...
even more sadly, although my commercial support team is being paid,
they dont perform nearly half as well as the gcc dev. does.
most sadly, however, is that even though the commercial stuff is paid
for (and therebye funding itself), the docs are shite!!! they are ambigous,
they are lacking in *real* information, and they can mostly only been
seen with a certain type of 'viewer' (windows "help" springs to mind), unlike
the gcc docs, which is copious, mostly accurate, thorough and viewable if
i ssh to the machine that it is stored on. it also means that the commercial
docs are not grep-able (*BIG* minus).
goose,
gcc does have its weaknesses, support isn't one of them ...