it's diffrent that(reffer to the reference1) ) TCC goes like
char* s -> char *dest
char* ct -> char *src
char * cs -> char *s
int c -> int c
NULL constant -> Null ((void *)0) or 0(what I would like to
write : ) )
and I just found a little more of this pattern
differences.
At this point, I know that there might be some
problem
if I keep on writting reffer to the reference1)
what do we do with double x, exp *stream, and so
on?
Won't there be any problem if I do insist to write in the
form
that the reference1) suggests?
(so something like... char *s, const char *t, *fcm, int status,
file *stream...)
I wondered that TCC supports any
other(ANSI C) header
function declerations
(C90 headers.. such as assert.h,cytpe.h,errono.h,float.h,limits.h,
locale.h,math.h,setjmp.h,signal.h,stdarg.h,
stddef.h,stddef.h,stdio.h,stdilib.h,string.h,time.h)
but it seems working somehow because
I wrote string.h for myself and TCC would give me a
segmentation fault without it.(ver. 0.9.0 of TCC)
Is there any good source or reference for writting this headers?
Any suggestions?
1)http://www.utas.edu.au/infosys/info/documentation/C/CStdLib.html