C Language, C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY

C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY

Author	Message
Philipp #1 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Does anyone already compare the 5 following products : SPLINT, PC-LINT, QA/C,POLYSPACE, PURIFY ? I know that the first one is free, and the 2 latest are expensive. Do they worth it ? I made few tests with SPLINT and it does NOT detect "easy" errors like out-of-bounds array access. I assume POLYSPACE and PURIFY detect them, but does PC-LINT detect them ? Best regards.
Sat, 26 Nov 2005 22:00:16 GMT

Jeff #2 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Quote: > Does anyone already compare the 5 following products : > SPLINT, PC-LINT, QA/C,POLYSPACE, PURIFY ? > I know that the first one is free, and the 2 latest are expensive. > Do they worth it ? > I made few tests with SPLINT and it does NOT detect "easy" errors like > out-of-bounds array access. > I assume POLYSPACE and PURIFY detect them, but does PC-LINT detect them ? > Best regards. Personally, I prefer "-Wall"
Sat, 26 Nov 2005 22:25:24 GMT

Dann Corbi #3 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Quote: > Does anyone already compare the 5 following products : > SPLINT, PC-LINT, QA/C,POLYSPACE, PURIFY ? > I know that the first one is free, and the 2 latest are expensive. > Do they worth it ? > I made few tests with SPLINT and it does NOT detect "easy" errors like > out-of-bounds array access. > I assume POLYSPACE and PURIFY detect them, but does PC-LINT detect them ? Different tool classes work to solve different problems. Runtime tools like purify detect runtime problems better. Static checkers like splint detect other sorts of difficulties. Sometimes, PC-Lint will see an array bounds access error, but not always. The best thing to do is fill your toolbox with tools, learn to use them properly, and choose the appropriate tool for the problem at hand. Profilers and coverage analyzers are also a very good idea. ---------------------------------------------------------------------------- - Les catgories diffrentes d'outil travaillent rsoudre des problmes diffrents. Courir les outils de temps comme purifie dtecte l'amliorer de problmes de temps de course. Les marqueurs statiques aiment que splint dtecte d'autres genres de difficults. Parfois, la PC BOURRE verra qu'un ensemble limite l'erreur d'accs, mais pas toujours. La meilleure chose faire est remplit votre bo?te outils avec les outils, apprendre les utiliser convenablement, et choisir l'outil correspondant pour le problme sous la main. Les analyseurs de Profilers et reportage sont aussi une trs bonne ide. -- C-FAQ: http://www.eskimo.com/~scs/C-faq/top.html "The C-FAQ Book" ISBN 0-201-84519-9 C.A.P. FAQ: ftp://cap.connx.com/pub/Chess%20Analysis%20Project%20FAQ.htm
Sun, 27 Nov 2005 01:32:52 GMT

Emmanuel Delahay #4 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Quote: > Les catgories diffrentes d'outil travaillent rsoudre des problmes > diffrents. Courir les outils de temps comme purifie dtecte l'amliorer > de problmes de temps de course. Les marqueurs statiques aiment que > splint dtecte d'autres genres de difficults. Parfois, la PC BOURRE > verra qu'un ensemble limite l'erreur d'accs, mais pas toujours. > La meilleure chose faire est remplit votre bo?te outils avec les > outils, apprendre les utiliser convenablement, et choisir l'outil > correspondant pour le problme sous la main. > Les analyseurs de Profilers et reportage sont aussi une trs bonne ide. LOL, I like automatic translators! It's always a great fun! -- -ed- emdel at noos.fr The C-language FAQ: http://www.eskimo.com/~scs/C-faq/top.html C-library: http://www.dinkumware.com/htm_cl/index.html FAQ de f.c.l.c : http://www.isty-info.uvsq.fr/~rumeau/fclc/ "Clearly your code does not meet the original spec." "You are sentenced to 30 lashes with a wet noodle." -- Jerry Coffin in a.l.c.c++
Sun, 27 Nov 2005 04:04:50 GMT

those who know me have no need of my nam #5 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY [fu-t set] in comp.lang.c i read: Quote: >> Does anyone already compare the 5 following products : >> SPLINT, PC-LINT, QA/C,POLYSPACE, PURIFY ? >> I know that the first one is free, and the 2 latest are expensive. >> Do they worth it ? >Personally, I prefer "-Wall" and -W and -ansi and -pedantic and -O and ... some can use valgrind to help them. -- a signature
Sun, 27 Nov 2005 04:21:19 GMT

Joona I Palast #6 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY on comp.lang.c: Quote: >> Les catgories diffrentes d'outil travaillent rsoudre des problmes >> diffrents. Courir les outils de temps comme purifie dtecte l'amliorer >> de problmes de temps de course. Les marqueurs statiques aiment que >> splint dtecte d'autres genres de difficults. Parfois, la PC BOURRE >> verra qu'un ensemble limite l'erreur d'accs, mais pas toujours. >> La meilleure chose faire est remplit votre bo?te outils avec les >> outils, apprendre les utiliser convenablement, et choisir l'outil >> correspondant pour le problme sous la main. >> Les analyseurs de Profilers et reportage sont aussi une trs bonne ide. > LOL, I like automatic translators! It's always a great fun! Why? Is the result of Dann's translation so bad? I don't know much French so I can't check for myself. -- \| Kingpriest of "The Flying Lemon Tree" G++ FR FW+ M- #108 D+ ADA N+++\| \| http://www.helsinki.fi/~palaste W++ B OP+ \| \----------------------------------------- Finland rules! ------------/ "That's no raisin - it's an ALIEN!" - Tourist in MTV's Oddities
Sun, 27 Nov 2005 13:50:31 GMT

Eddahbi Kari #7 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Le Wed, 11 Jun 2003 05:50:31 +0000, Joona I Palaste a crit?: Quote: > on comp.lang.c: >>> Les catgories diffrentes d'outil travaillent rsoudre des problmes >>> diffrents. Courir les outils de temps comme purifie dtecte l'amliorer >>> de problmes de temps de course. Les marqueurs statiques aiment que >>> splint dtecte d'autres genres de difficults. Parfois, la PC BOURRE >>> verra qu'un ensemble limite l'erreur d'accs, mais pas toujours. >>> La meilleure chose faire est remplit votre bo?te outils avec les >>> outils, apprendre les utiliser convenablement, et choisir l'outil >>> correspondant pour le problme sous la main. >>> Les analyseurs de Profilers et reportage sont aussi une trs bonne ide. >> LOL, I like automatic translators! It's always a great fun! > Why? Is the result of Dann's translation so bad? I don't know much > French so I can't check for myself. It's as bad as French to english translations with some softwares :D.
Sun, 27 Nov 2005 15:14:11 GMT

Joona I Palast #8 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY on comp.lang.c: Quote: > Le Wed, 11 Jun 2003 05:50:31 +0000, Joona I Palaste a crit?: >> on comp.lang.c: >>>> Les catgories diffrentes d'outil travaillent rsoudre des problmes >>>> diffrents. Courir les outils de temps comme purifie dtecte l'amliorer >>>> de problmes de temps de course. Les marqueurs statiques aiment que >>>> splint dtecte d'autres genres de difficults. Parfois, la PC BOURRE >>>> verra qu'un ensemble limite l'erreur d'accs, mais pas toujours. >>>> La meilleure chose faire est remplit votre bo?te outils avec les >>>> outils, apprendre les utiliser convenablement, et choisir l'outil >>>> correspondant pour le problme sous la main. >>>> Les analyseurs de Profilers et reportage sont aussi une trs bonne ide. >>> LOL, I like automatic translators! It's always a great fun! >> Why? Is the result of Dann's translation so bad? I don't know much >> French so I can't check for myself. > It's as bad as French to english translations with some softwares :D. Could you point out some parts in Dann's post that are specially bad? And provide better translations? Thanks. -- \| Kingpriest of "The Flying Lemon Tree" G++ FR FW+ M- #108 D+ ADA N+++\| \| http://www.helsinki.fi/~palaste W++ B OP+ \| \----------------------------------------- Finland rules! ------------/ "Remember: There are only three kinds of people - those who can count and those who can't." - Vampyra
Sun, 27 Nov 2005 15:19:14 GMT

Zoran Cutur #9 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Quote: > on comp.lang.c: >> Le Wed, 11 Jun 2003 05:50:31 +0000, Joona I Palaste a ?crit?: ... >>> Why? Is the result of Dann's translation so bad? I don't know much >>> French so I can't check for myself. >> It's as bad as French to english translations with some softwares :D. > Could you point out some parts in Dann's post that are specially bad? > And provide better translations? Thanks. Could you guys please take your French lessons to private mail or a french learning newsgroup? -- "LISP is worth learning for the profound enlightenment experience you will have when you finally get it; that experience will make you a better programmer for the rest of your days." -- Eric S. Raymond
Sun, 27 Nov 2005 15:16:31 GMT

Joona I Palast #10 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY on comp.lang.c: Quote: >> on comp.lang.c: >>> Le Wed, 11 Jun 2003 05:50:31 +0000, Joona I Palaste a ?crit?: > ... >>>> Why? Is the result of Dann's translation so bad? I don't know much >>>> French so I can't check for myself. >>> It's as bad as French to english translations with some softwares :D. >> Could you point out some parts in Dann's post that are specially bad? >> And provide better translations? Thanks. > Could you guys please take your French lessons to private mail or a > french learning newsgroup? Sorry about that. I've set followups of this message to fr.comp.lang.c only. Please answer my question there or e-mail me directly. Thanks. -- \| Kingpriest of "The Flying Lemon Tree" G++ FR FW+ M- #108 D+ ADA N+++\| \| http://www.helsinki.fi/~palaste W++ B OP+ \| \----------------------------------------- Finland rules! ------------/ "How come even in my fantasies everyone is a jerk?" - Daria Morgendorfer
Sun, 27 Nov 2005 15:43:41 GMT

Richard Delorm #11 / 11	C code check : SPLINT versus PC-LINT versus QA/C versus POLYSPACE versus PURIFY Joona I Palaste a crit: Quote: > Could you point out some parts in Dann's post that are specially bad? > And provide better translations? Thanks. >> Les catgories diffrentes d'outil travaillent rsoudre des >> problmes diffrents. This one is acceptable, although not perfect. Quote: >> Courir les outils de temps comme purifie dtecte >> l'amliorer de problmes de temps de course. Here "runtime" has been translated as "racing time" instead of "during execution" Quote: >> Les marqueurs statiques "checkers" has been translated as "markers" instead of programs that "verify, control" things Quote: >> aiment que splint dtecte d'autres genres de difficults. Parfois, la Here "like" has been used as the verb "to like" meaning "static checkers that love splint...". Quote: >> PC BOURRE verra qu'un ensemble limite l'erreur d'accs, mais pas >> toujours. The meaning of the sentence is "PC-FUZZ will see that a set limits the access error" Quote: >> La meilleure chose faire est remplit votre bo?te outils avec les >> outils, apprendre les utiliser convenablement, et choisir l'outil >> correspondant pour le problme sous la main. s/remplit/remplir. Acceptable, although not "good" French. Quote: >> Les analyseurs de Profilers et reportage sont aussi une trs bonne >> ide. "coverage" has been translated as a "journalistic report". Here is a trial for a better french translation : ? A chaque problme son outil. Les outils dynamiques comme Purify dtectent mieux les problmes d'excution. Les outils statiques comme splint dtectent d'autres types de difficults. Parfois, PC-Lint verra une erreur d'accs hors limites un tableau, mais pas toujours. Le mieux est de se munir de ces outils, d'apprendre les utiliser convenablement, et de choisir l'outil appropri au problme rencontr. Les profileurs et les analyseurs d'utilisation du code sont aussi une trs bonne ide. ? -- Richard
Sun, 27 Nov 2005 16:29:16 GMT

Page 1 of 1

[ 11 post ]