Re: Coroutines w (GNU) C

Article View: pl.comp.lang.c

Article #310073

#310073

From: heby
Date: Mon, 27 Jan 2020 18:11

7 lines
1504 bytes

On 27/01/2020 07:53, Maciek Godek wrote:
> Moje rozwiązanie jest dla C.

A po co? W systemach gdzie się przydaje na 100% jest C++. W 99.9% 
wypadków wystarczy zamienić gcc na g++.

Po co komu coroutines w C skorą są/będą w C++?

Technical Details

Message-ID: <r0n95e$35l$1@dont-email.me>

Path:

mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail

References:

<4375b52d-ba21-462a-8844-9bd1a02e9ece@googlegroups.com> <r0k8i5$ifg$1@dont-email.me> <ce3f0b08-658f-4248-b82c-09f093a7f20c@googlegroups.com> <r0kq6d$v6h$1@dont-email.me> <748c5d16-f4a8-43a0-8a56-bea0800e1e04@googlegroups.com>

Show Full Headers

Complete Article Headers

Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!newsfeed.pionier.net.pl!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: heby <heby@poczta.onet.pl>
Newsgroups: pl.comp.lang.c
Subject: Re: Coroutines w (GNU) C
Date: Mon, 27 Jan 2020 19:11:59 +0100
Organization: A noiseless patient Spider
Lines: 7
Message-ID: <r0n95e$35l$1@dont-email.me>
References: <4375b52d-ba21-462a-8844-9bd1a02e9ece@googlegroups.com> <r0k8i5$ifg$1@dont-email.me> <ce3f0b08-658f-4248-b82c-09f093a7f20c@googlegroups.com> <r0kq6d$v6h$1@dont-email.me> <748c5d16-f4a8-43a0-8a56-bea0800e1e04@googlegroups.com>
Mime-Version: 1.0
Injection-Date: Mon, 27 Jan 2020 18:11:58 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="a142005fc87d8a3409f6f9b4ffde8cce"; logging-data="3253"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18t+7lqLH1xp9xHD6IWGBjT"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
Cancel-Lock: sha1:J7nUk95tam6VfpFkY5G7IPkk/yI=
In-Reply-To: <748c5d16-f4a8-43a0-8a56-bea0800e1e04@googlegroups.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Reply to Parent Message