Deutsch English Français Italiano |
<v4a0ck$1569e$1@dont-email.me> View for Bookmarking (what is this?) Look up another Usenet article |
Path: ...!feed.opticnetworks.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: bart <bc@freeuk.com> Newsgroups: comp.lang.c Subject: Re: Baby X is bor nagain Date: Tue, 11 Jun 2024 18:09:41 +0100 Organization: A noiseless patient Spider Lines: 32 Message-ID: <v4a0ck$1569e$1@dont-email.me> References: <v494f9$von8$1@dont-email.me> <v49seg$14cva$1@raubtier-asyl.eternal-september.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Tue, 11 Jun 2024 19:09:40 +0200 (CEST) Injection-Info: dont-email.me; posting-host="88742f5eb613ac2c5fda4e8fbeef6441"; logging-data="1218862"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ImvP9HmFzSvFMJw+et20p" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:hPvZEmKzuGbscqJAlq+dYASUXMA= Content-Language: en-GB In-Reply-To: <v49seg$14cva$1@raubtier-asyl.eternal-september.org> Bytes: 2299 On 11/06/2024 17:02, Bonita Montero wrote: > Am 11.06.2024 um 11:13 schrieb Malcolm McLean: > >> I've finally got Baby X (not the resource compiler, the Windows >> toolkit) to link X11 on my Mac. And I can start work on it again. But >> it was far from easyt to get it to link. >> Can friendly people plesse dowload it and see if it compiles on other >> platforms? > > For large files it would be more convenient to have an .obj-output in > the proper format for Windows or Linux. I implemented a binary file to > char-array compiler myself and for lage files the compilation time was > totally intolerable and all the compilers I tested (g++, clang++, MSVC) > ran into out of memory conditiond sooner or later, depending on the > size of the char array. A char array initialised a byte at a time? That is going to be inefficient. Instead of a large array like {65, 65, 66 ...} try instead generating a single string like: "\101\102\103..." "\x41\x42\x43..." Or maybe numbers of shorter strings with a few dozen values per line. Each string should be represented internally by the compiler as a single object occupying one byte per element, instead of dozens or even hundreds of bytes per element.