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

Groups > comp.lang.c > #129981

Re: Clearly everyone else likes to do things the hard way

From scott@slp53.sl.home (Scott Lurndal)
Subject Re: Clearly everyone else likes to do things the hard way
Newsgroups comp.lang.c
References (7 earlier) <ad6cre-s03.ln1@tanner.seckford.org> <rL_EC.53102$7B3.31501@fx13.am4> <944e11bd-156f-4237-a7d3-7fe8df6ff7e6@googlegroups.com> <hrJFC.29444$7b4.26558@fx12.am4> <140da57f-8089-4998-9a52-0f8019d107c9@googlegroups.com>
Message-ID <IWJFC.15749$3R1.2222@fx16.iad> (permalink)
Organization UsenetServer - www.usenetserver.com
Date 2018-04-30 19:14 +0000

Show all headers | View raw

supercat@casperkitty.com writes:
>On Monday, April 30, 2018 at 1:41:25 PM UTC-5, Bart wrote:
>> Translated to C however, it is just one file (of size 0.5MB), 
>> which includes this line:
>> 
>> static char * sourcecode="/* MCC Experimental C Compiler\r\n\r\n .... "
>> 
>> which is 480,000 characters long (somewhat longer than the original 
>> because of the escape codes).
>> 
>> Compiling that C version and running it also works. Since this is a C 
>> program, and a small one apart from the string, it can be written in 
>> portable code (another than the need to deal with very long strings), 
>> and can interrogate the host system for the most appropriate C compiler 
>> settings. And then build the real program.
>
>Using a string literal would require that the entire program be capable of
>fitting in memory.  Depending upon the size of the program and the target
>platform, that may or may not be a problem.  I would expect that most
>implementations would be capable of handling an almost-arbitrarily-large
>comment within any source file whose total size was less than 2GiB, even
>if they couldn't handle strings anywhere near that big.  Using a separate
>data file rather than a comment might improve efficiently a tiny bit (by
>eliminating the need to have a compiler skip over a giant comment) but
>would make it necessary to keep the program and its data file "in sync".
>
>BTW, I would think compiler performance in many of situations could be
>improved if the Standard were to define a directive:
>
>#pragma STDC_SKIP_REMAINDER
>
>which, at a compiler's option, could either do nothing or behave as though
>the balance of the source file contained nothing except sufficient #endif
>directives to balance out any preceding #if directives.  Existing compilers
>wouldn't have to do anything to be compatible with such a directive, but
>replacing
>
>    #if !defined(FOO_H)
>    #define FOO_H
>    ...
>    #endif
>
>with
>
>    #if defined(FOO_H)
>    #pragma STDC_SKIP_REMAINDER
>    #else
>    #define FOO_H
>    ...
>    #endif
>
>could improve compilation performance in cases where foo.h gets included
>from multiple places while processing a translation unit, since a compiler
>wouldn't have to read through the #else block to find the #endif.

Maybe in 1984.   Today it would be unnoticable.

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

Thread

gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 16:21 +0100
  gcc_centric C code Chad <cdalten@gmail.com> - 2018-04-25 08:34 -0700
  Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-25 16:41 +0100
    Re: gcc_centric C code Spiros Bousbouras <spibou@gmail.com> - 2018-04-25 16:19 +0000
      Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 18:02 +0100
        Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 17:15 +0000
          Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 12:33 -0500
          Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 20:51 +0100
            Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 13:01 -0700
              Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 21:21 +0100
            Re: gcc_centric C code jameskuyper@verizon.net - 2018-04-25 13:45 -0700
        Re: gcc_centric C code Spiros Bousbouras <spibou@gmail.com> - 2018-04-25 17:20 +0000
      Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 10:30 -0700
        Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 12:35 -0500
          Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 10:54 -0700
            Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-25 20:27 +0200
              Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 12:38 -0700
              Re: gcc_centric C code Robert Wessel <robertwessel2@yahoo.com> - 2018-04-25 19:53 -0500
                Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 18:13 -0700
                Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-26 15:16 +0000
                Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 08:17 -0700
                Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 08:03 +0200
                Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-26 14:30 +0000
                Re: gcc_centric C code jameskuyper@verizon.net - 2018-04-26 08:26 -0700
                Re: gcc_centric C code Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 19:04 +0200
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 07:48 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 21:08 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 08:18 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 21:44 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 09:01 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:16 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 10:27 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:48 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-27 20:41 +1200
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 11:51 +0100
                Re: gcc_centric C code Ian Collins <ian-news@hotmail.com> - 2018-04-28 07:32 +1200
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-28 04:34 -0700
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 23:05 -0700
                Re: gcc_centric C code jacobnavia <jacob@jacob.remcomp.fr> - 2018-04-27 00:52 +0200
                Re: gcc_centric C code supercat@casperkitty.com - 2018-04-26 16:23 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-28 11:24 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-28 01:42 +0100
                Re: gcc_centric C code Dan Purgert <dan@djph.net> - 2018-04-26 21:40 +0000
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 23:34 +0100
                Re: gcc_centric C code "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-26 14:13 -0700
                Re: gcc_centric C code "Chris M. Thomasson" <invalid_chris_thomasson@invalid.invalid> - 2018-04-26 14:16 -0700
            Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 08:08 -0700
              Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-27 09:11 -0700
                Re: gcc_centric C code supercat@casperkitty.com - 2018-04-27 09:26 -0700
                Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 09:49 -0700
          Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 12:31 -0700
            Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 20:13 +0000
              Re: gcc_centric C code supercat@casperkitty.com - 2018-04-25 13:50 -0700
        Re: gcc_centric C code Nick Bowler <nbowler@draconx.ca> - 2018-04-25 18:02 +0000
      Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-25 22:39 -0700
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-25 18:36 +0100
      Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-25 23:15 +0100
        Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 02:02 +0100
          Re: gcc_centric C code Keith Thompson <kst-u@mib.org> - 2018-04-25 18:28 -0700
          Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-26 11:45 +0100
            Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 14:53 +0100
              Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-26 23:38 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 00:31 +0100
                Re: gcc_centric C code Ben Bacarisse <ben.usenet@bsb.me.uk> - 2018-04-27 00:47 +0100
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 02:28 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-04-27 03:44 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-05-03 13:57 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 11:02 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 11:07 -0700
                Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-05-03 11:13 -0700
                Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-05-03 19:50 +0100
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 13:37 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-03 13:44 -0700
                Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-05-11 10:25 -0700
            Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 07:01 -0700
          Re: Clearly everyone else likes to do things the hard way Noob <root@127.0.0.1> - 2018-04-26 14:51 +0200
            Re: Clearly everyone else likes to do things the hard way mark.bluemel@gmail.com - 2018-04-26 07:09 -0700
              Re: Clearly everyone else likes to do things the hard way gazelle@shell.xmission.com (Kenny McCormack) - 2018-04-26 17:05 +0000
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-26 18:38 +0100
                Re: Clearly everyone else likes to do things the hard way 1alvinalbrecht1@gmail.com - 2018-04-26 11:34 -0700
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-26 21:36 +0100
                Re: Clearly everyone else likes to do things the hard way C W Rose <cwr@seckford.org> - 2018-04-27 19:23 +0100
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-28 14:34 +0100
                Re: Clearly everyone else likes to do things the hard way Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-28 10:32 -0700
                Re: Clearly everyone else likes to do things the hard way supercat@casperkitty.com - 2018-04-30 10:16 -0700
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-30 19:41 +0100
                Re: Clearly everyone else likes to do things the hard way supercat@casperkitty.com - 2018-04-30 12:11 -0700
                Re: Clearly everyone else likes to do things the hard way scott@slp53.sl.home (Scott Lurndal) - 2018-04-30 19:14 +0000
                Re: Clearly everyone else likes to do things the hard way scott@slp53.sl.home (Scott Lurndal) - 2018-04-30 19:12 +0000
                Re: Clearly everyone else likes to do things the hard way bartc <bc@freeuk.com> - 2018-04-30 21:19 +0100
                Re: Clearly everyone else likes to do things the hard way Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-30 19:23 -0700
                Re: Clearly everyone else likes to do things the hard way Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 19:45 +0200
      Re: gcc_centric C code luser droog <luser.droog@gmail.com> - 2018-04-25 21:56 -0700
        Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 11:06 +0100
          Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 11:27 +0100
      Re: gcc_centric C code antispam@math.uni.wroc.pl - 2018-04-26 17:00 +0000
  Re: gcc_centric C code Thiago Adams <thiago.adams@gmail.com> - 2018-04-25 09:26 -0700
  Re: gcc_centric C code Jorgen Grahn <grahn+nntp@snipabacken.se> - 2018-04-26 12:39 +0000
    Re: gcc_centric C code gazelle@shell.xmission.com (Kenny McCormack) - 2018-04-26 13:09 +0000
  Re: gcc_centric C code Wouter Verhelst <w@uter.be> - 2018-04-26 13:26 +0200
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-26 18:03 +0100
    Re: gcc_centric C code Steven Petruzzellis <frelwizzen@gmail.com> - 2018-04-26 14:32 -0700
  Re: gcc_centric C code Tim Rentsch <txr@alumni.caltech.edu> - 2018-04-27 09:41 -0700
    Re: gcc_centric C code bartc <bc@freeuk.com> - 2018-04-27 19:37 +0100

csiph-web