[comp.realtime] lint for QNX

pte900@jatz.aarnet.edu.au (Peter Elford) (06/04/91)

Does anybody know if there is a lint for QNX out there somewhere ?

[ posted on behalf of someone else ]

Peter Elford,                           	e-mail: P.Elford@aarnet.edu.au
Network Co-ordinator,	 			phone: +61 6 249 3542
Australian Academic Research Network,		fax:   +61 6 247 3425
c/o, Computer Services Centre,			pager: +61 6 245 3035
Australian National University			post:	PO Box 4     
Canberra, AUSTRALIA					Canberra 2601

gardner@isdc11.kodak.com (Dick Gardner) (06/05/91)

In article <1991Jun4.005018.11404@newshost.anu.edu.au> P.Elford@aarnet.edu.au writes:
>Does anybody know if there is a lint for QNX out there somewhere ?
>
--------------------------------------------------

	tried to mail this, but mailer must be dain-bramaged

--------------------------------------------------
Peter 

	Computer Innovations makes a product called Flexelint for QNX.
However, it supports their C-86 Complier for QNX, and not the Quantum 
compiler.

	They are going to be at the QNX conference in Ottawa during
June 17-20.

	Their address is:

		Computer Innovations Inc.
		980 Shrewsbury Avenue
		Tinton Falls, New Jersey 
				07724-3003 USA
		FAX: (210) 542-6121

	I am not aware of any version of lint for the Quantum compiler.

Hope this is useful information,

=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#
   Dick Gardner -- Eastman Kodak Co.  Rochester, New York  14652-4201
                   Phone: (716) 477-1002
		   Net address:  gardner@music.kodak.com

	My new whiz-bang computer is SOOOOOOO fast ----
	  (How fast is it??)	it executes an infinite loop in 50 msec!!!

=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#=#
  

manning@nntp-server.caltech.edu (Evan Marshall Manning) (06/05/91)

gardner@isdc11.kodak.com (Dick Gardner) writes:

>In article <1991Jun4.005018.11404@newshost.anu.edu.au> P.Elford@aarnet.edu.au writes:
>>Does anybody know if there is a lint for QNX out there somewhere ?
>>
>--------------------------------------------------

>	tried to mail this, but mailer must be dain-bramaged

>--------------------------------------------------
>Peter 

>	Computer Innovations makes a product called Flexelint for QNX.
>However, it supports their C-86 Complier for QNX, and not the Quantum 
>compiler.

Computer innovations may *market* Flexilint for QNX, but Gimpel makes it.
The "flexi" is short for "flexible", and unless the Quantum compiler is
very nonstandard, flexilint should work just fine for it too, as long as
you create the appropriate compiler description file (with int size,
char signedness, etc).

Gimpel distributes it in "shrouded source" form, so it can be run on
any platform with a C compiler.

Remember lint is largely a portablility tool so it needn't be rewritten
for each compiler.

You can contact the nice people at Gimpel:

	Gimpel Software
	3207 Hogarth Lane
	Collegeville, PA 19429
	(215) 584-4261

Me?  I'm a satisfied customer of their PC product, PC-lint.

***************************************************************************
Your eyes are weary from staring at the CRT for so | Evan M. Manning
long.  You feel sleepy.  Notice how restful it is  |      is
to watch the cursor blink.  Close your eyes.  The  | manning@gap.caltech.edu
opinions stated above are yours.  You cannot       | manning@mars.jpl.nasa.gov
imagine why you ever felt otherwise.               | gleeper@tybalt.caltech.edu
i=3;do{putchar(((0x18|1<<!(i&2)|(!!i==i)*2)<<2|2>>i%2)^(2<<1+i));}while(i--);

gordd@geovision.gvc.com (Gord Deinstadt) (06/07/91)

manning@nntp-server.caltech.edu (Evan Marshall Manning) writes:

>Computer innovations may *market* Flexilint for QNX, but Gimpel makes it.
>The "flexi" is short for "flexible", and unless the Quantum compiler is
>very nonstandard, flexilint should work just fine for it too, as long as
>you create the appropriate compiler description file (with int size,
>char signedness, etc).

Wellll, "old" (pre-4.0) QNX C has:

@ and -} operators for extra-segment access, and

long foo = 'ABCD';
short bar = 'AB';

and it lets you get away with non-Ascii characters in strings, which
I have seen used for non-English language support.

But if you stick to the standard subset you should be all right.
--
Gord Deinstadt  gdeinstadt@geovision.gvc.com