Date: Sat, 23 Sep 2023 14:04:41 -0700
On Saturday, 23 September 2023 05:09:31 PDT Frederick Virchanza Gotham via
Std-Proposals wrote:
> Give me a link to one of those Chromium source files, I'll run it through a
> preprocessor to get a translation unit, and then I'll run my own
> proprietary parser on it to get all the types -- let's see if it's in the
> thousands, and let's see how many of the implementations have identical
> machine code.
The source code for Chromium is readily available on the Internet. It's not at
all easy to build (you need Node.js to generate the build files), but it's
doable and lots of people do it every day.
Anyway, if after the feedback you've already received you still think this is
an idea worth pursuing, I suggest you implement it in one of the compilers and
see if it can be done with
a) reasonable amount of memory for the compiler
b) reasonable time spent compiling
c) non-explosive code expansion in the resulting binaries
Std-Proposals wrote:
> Give me a link to one of those Chromium source files, I'll run it through a
> preprocessor to get a translation unit, and then I'll run my own
> proprietary parser on it to get all the types -- let's see if it's in the
> thousands, and let's see how many of the implementations have identical
> machine code.
The source code for Chromium is readily available on the Internet. It's not at
all easy to build (you need Node.js to generate the build files), but it's
doable and lots of people do it every day.
Anyway, if after the feedback you've already received you still think this is
an idea worth pursuing, I suggest you implement it in one of the compilers and
see if it can be done with
a) reasonable amount of memory for the compiler
b) reasonable time spent compiling
c) non-explosive code expansion in the resulting binaries
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Software Architect - Intel DCAI Cloud Engineering
Received on 2023-09-23 21:04:43