Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #105485

Re: Problems with lcc-win32

Show all headers | View raw

On 06/03/17 15:54, jm.bourguet@gmail.com wrote:
> Le lundi 6 mars 2017 04:34:07 UTC+1, Keith Thompson a écrit :
>> In my opinion a missing include file should be a fatal error.
> 
> Shared.  I don't even like the long list of errors which sometimes
> follow an header not found.  They are by-product of the first error
> and thus pure noise.  As that noise come closer to the first place I
> see -- then end of the compilation log -- I've lost too much time
> finding out that the root cause was a previous signaled error.
> (There are errors for which it is meaningful to continue the
> compilation and signal subsequent one, IMHO this is not one)
> 
>> Feel free to consider the fact that I'm not an lcc-win user in
>> deciding how to deal with this.
> 
> Neither am I.
> 
>> On the other hand, some kind of conditional include might be a
>> useful extension, perhaps something like:
>> 
>> #include_if_exists <some_header.h>
>> 
>> and/or
>> 
>> #if_header_exists <some_header.h>
> 
> C++ has added __has_include(<some_header.h>).

C++ does not have "__has_include".  A number of C++ compilers (gcc,
clang, MSVC, perhaps others) have it as an extension - for gcc and clang
it works in C as well as C++, but I don't know about MSVC.

With that correction, I agree that it would be the best choice for such
an extension - as I already wrote in a previous post.

>  If you create an
> extension, I'd suggest looking at the previous art that was
> normalized in that language related to C, there has already been
> quite a lot of inspiration both way and as a user of both, the cases
> when the later one choose to do something more or less subtly
> differently than the precursor are painful (I'm thinking of inline,
> where the issue is made worse by the fact it often would have been
> meaningful in a shared header if the C definition had followed C++
> one). The preprocessor is a case where this make even more sense as
> there is very few things there which are dependent on the language.
> 
> Yours,
> 

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Problems with lcc-win32 mertesthomas@gmail.com - 2017-03-05 14:12 -0800
  Re: Problems with lcc-win32 luser droog <luser.droog@gmail.com> - 2017-03-05 14:46 -0800
    Re: Problems with lcc-win32 gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-05 22:57 +0000
    Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:49 +0100
      Re: Problems with lcc-win32 luser droog <luser.droog@gmail.com> - 2017-03-05 22:10 -0800
  Re: Problems with lcc-win32 BartC <bc@freeuk.com> - 2017-03-05 23:32 +0000
    Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:48 +0100
  Re: Problems with lcc-win32 jacob navia <jacob@jacob.remcomp.fr> - 2017-03-06 00:44 +0100
    Re: Problems with lcc-win32 BartC <bc@freeuk.com> - 2017-03-06 00:13 +0000
    Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-05 19:35 -0800
      Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 10:26 +0100
        Re: Problems with lcc-win32 James Kuyper <jameskuyper@verizon.net> - 2017-03-06 07:08 -0500
        Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-06 08:37 -0800
          Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:16 +0100
      Re: Problems with lcc-win32 jm.bourguet@gmail.com - 2017-03-06 06:54 -0800
        Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 17:18 +0100
          Re: Problems with lcc-win32 Keith Thompson <kst-u@mib.org> - 2017-03-06 08:42 -0800
            Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:19 +0100
          Re: Problems with lcc-win32 jm.bourguet@gmail.com - 2017-03-06 08:44 -0800
            Re: Problems with lcc-win32 David Brown <david.brown@hesbynett.no> - 2017-03-06 21:20 +0100
    Re: Problems with lcc-win32 mertesthomas@gmail.com - 2017-03-06 00:24 -0800
  Re: Problems with lcc-win32 jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-06 18:15 +0100
    Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-06 18:50 +0100
      Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 04:50 -0800
        Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-07 14:54 +0100
          Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 06:20 -0800
            Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-07 15:02 +0000
              Re: Problems with lcc-win32 (trimmed) mertesthomas@gmail.com - 2017-03-07 08:00 -0800
                Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-07 20:30 +0100
                Re: Problems with lcc-win32 (trimmed) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-08 01:06 +0000
                Re: Problems with lcc-win32 (trimmed) jacobnavia <jacob@jacob.remcomp.fr> - 2017-03-08 12:17 +0100
                Assigning a struct to an integer (Was: Problems with lcc-win32 (trimmed)) gazelle@shell.xmission.com (Kenny McCormack) - 2017-03-08 11:40 +0000
                Re: Problems with lcc-win32 (trimmed) Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-03-08 11:51 +0000
              Re: Problems with lcc-win32 (trimmed) Robert Wessel <robertwessel2@yahoo.com> - 2017-03-07 15:27 -0600
                Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-08 13:50 +0000
                Re: Problems with lcc-win32 (trimmed) scott@slp53.sl.home (Scott Lurndal) - 2017-03-08 13:51 +0000

csiph-web