Re: [Tinycc-devel] How to use char "\"

[JFC Morfin]

Hi! Evan,

At 19:30 30/09/2014, Evan Langlois wrote:
> However, strpbrk doesn't accept a regex or shell globs.  I don't see 
> why you would be checking for '*' or '?' in a filename!

This is to check it is a real file name, and not a regex.

> If TCC says \* is an unknown escape sequence then that looks like 
> exactly what it should be doing.  There is no such escape.
> As for text[i]='\\', I'm betting when he says "do not work" its a 
> run-time error due to a bug in his code, not a TCC bug.

The question is not about bugs. These are ten years old libraries 
used millions of time but compiled under Borland. There are 
differences between compilers. The question is only to understand them.

> On Tue, Sep 30, 2014 at 12:29 PM, Jefsey <address@hidden> wrote:
> > Thank you all. The problem the I have is that I am quite rusty at 
> > my C and TCC is new to me :-) 1. First thing is that I use "tcc 
> > xxxx.c" and I do not know how to get more than one kind of error at 
> > a time? Is there a way to have all the compilation errors one shot in a file ?
>
> tcc file.c >output.txt

Thx.
1. What  I suspect is that TCC only reports a kind of compilation 
error at a time not all of them.
For example when I tried to address the "\" issue, it did not report 
on "isascii".
Is there a way to tell TCC to continue trying to compile even after 
"blocking" errors. This was by default in BCC and several others.

2. Sometimes you can have the kind of report above not displayed on 
the screen but directly sent in a file (because it may be rather 
long). Just asking.

> Uhmm ... and what escape is \. supposed to be?  You are confusing C 
> escapes with regular expressions I think.

This depends on compilers. In other compiler or environnement you 
must escape more things. In BCC these escapes are required

> > 3. The error I am reported now is that "isascii" us an unknopwn symbol.
>
> Did you include <ctype.h> ??

Sure. And isascii is documented there.

> Test your code with gcc please.  If it compiles under gcc and then 
> fails under tcc, then this is the proper list.  If it won't compile 
> under gcc, then perhaps stackoverflow would be a better place for help.

My choice of TCC is to avoid GCC :-) There are declaration 
discrepancies and they have used some function names I also used. If 
I could stay with tcc it would be simpler.

Take care and thanks
jfc