#curses
15 messages in this thread
My cousin is still eager for that real cheap curses package from Lattice
that cost only $125.00 that you mentioned in the Febuary issue. Where did
you find it?
The curses library comes with the Lattice C compiler. Lattice sells the
source code to the library for $125.00.
Al Stevens
Is it possible for a compiler to check types across modules? What about
against assembly files? -Martin
Type-checking across separately compiled modules normally can occur only
during link-time, if at all.
As for assembly files, normally that cannot be done, as most assemblers
don't provide ways of specifying typing information.
Joe
Joe ,
So if you want type checking from a high-level langauage to an assembler
file, you should definitely include a .h – type file? Any other ways you
can think of? -Martin
Martin,
In general, that's the only way to do it (i.e. have the high-level
language "assume" it knows what the types are). Some development systems
may allow for explicit typechecking, but most do not, so the only way to do
it is to tell the high-level language(s) what they are, and maintain those
include files with the assembler source.
Joe
Hi Joe,
I'm not real big on assembler. Is there some way of specifying a type in
assembler? I knwo that .OBJ's can hold info in TYPDEF records, but can you
specify that in ASM? We're talking about what gets passed to and from
functions…. -Martin
Martin,
I believe I keep saying this (although I may be thinking of the wrong
thread and/or forum), but there is no standard way of specifying data types
in assembly language. Some assemblers may do this, however — it depends
on the assembler. I know the two main Macintosh assemblers (MDS and MPW's
assembler) do not. As I do not work with MeSs-DOS machines, I cannot speak
for them.
Joe
How could there be? There are no standard machines.
A good lint will check many things in C across files. Some are available
that support ANSI headers & types.
If a compiler supports the ANSI spec 100%, how much use would a lint be?
_martin
Some of them will catch things like using pointers to free'd memory, and
constructs like "if(a=b)".
Turbo C handles the if (a=b) case with a warning:
"Possibly incorrect assignment"
JIM
TopSpeed C has an option to warn you about "Assignment in Test Expression"
which has saved me a number of times, since I program mainly in Modula-2.
-martin JPI
lint doesn't check for standards, Martin. It basically checks type
compatibilities and what-not about as thoroughly as Pascal does. The big
difference is that you can choose whether to ignore lint or not, where
Pascal doesn't give you that choice.
Joe