lint on Altos 2000 is BROKE BROKE BROKE!

[Jim Rosenberg]

Here is a wee little piece of C:

t0.c:
#include <stdio.h>

struct shmoo {
	int whoo;
	char noo;
};

extern struct shmoo *scroo;

char *foo()
{
	(void) fprintf(stderr, "I don't belive this!\n");
	return (char *) scroo;
}

Below is what lint -u t0.c says about it on our system, which is an Altos
2000 running Xenix System V/386 v5.2c:

t0.c
==============
warning: illegal pointer combination
    (13)  	


==============
function argument ( number ) used inconsistently
    fprintf( arg 1 )   	llibc(259) :: t0.c(12)


I don't believe this!!!  Complaining because a struct * is cast to a char *??
On my AT&T 3B1 lint is perfectly happy with this, as it should be.  But really:
lint doesn't know that stderr is a real live genuine (FILE *) ????

HELLLLLLLLLLLLP!!

Am I missing something?

Now that brings up another question.  Altos seems to have this nasty habit of
not wanting to listen to you if you don't have a support contract.  It makes
me furious to think I have to have a support contract to report bugs.  The
Altos 2000 is a peach of a machine, but I've found *several* of the utilities
that were broken.  Before it hasn't been any problem because I replaced them
with PD alternatives that are better anyway.  But I can hardly replace lint!
Anybody out there have any clout with Altos?
-- 
Jim Rosenberg                        pitt
Oglevee Computer Systems                 >--!amanue!oglvee!jr
151 Oglevee Lane                      cgh
Connellsville, PA 15425                                #include <disclaimer.h>