typedef laxity

[00704a-Liber]

In article <1071 at maynard.BSW.COM> campbell at maynard.UUCP (Larry Campbell) writes:

>Can anyone convince me that
>it shouldn't?  (For example, show me a code fragment where it is both
>reasonable and readable to mix type names as in the above example.)

Here is one that I see a lot among beginning C programmers:

	typedef	char *	string;

If I have the following declaration:

	string	foo;

I really don't want

	foo = "bar";

to be an error or even a warning from lint.
-- 
 _ __			NEVIN J. LIBER	..!ihnp4!ihlpf!nevin1	(312) 510-6194
' )  )				"The secret compartment of my ring I fill
 /  / _ , __o  ____		 with an Underdog super-energy pill."
/  (_</_\/ <__/ / <_	These are solely MY opinions, not AT&T's, blah blah blah