[HelenOS-devel] Replacing https://code.launchpad.net/helenos

Hi, so with Bazaar and Launchpad, the nice feature was that people could register branches lp:~user/helenos/foo and by looking at https://code. launchpad.net/helenos we could see all the latest helenos code activity in all related branches. Is there any way to achieve something similar with Git

Re: [HelenOS-devel] Replacing https://code.launchpad.net/helenos

Thanks. Too bad Github doesn't allow me to claim my commits as it does not consider jiri@wiwaxia a valid e-mail address :-) Cheers, Jiri -- Původní e-mail -- Od: Jakub Jermář Komu: helenos-devel@lists.modry.cz Datum: 15. 11. 2017 21:47:34 Předmět: Re:

[HelenOS-devel] What is wrong with restrict parameters?

Hello Jiri, I have noticed the following commit [1] where the restrict keyword was replaced with __restrict__ in multiple headers. I was wondering what is the reason for replacing C99 standard keyword with a proprietary extension (though implemented both by GCC and clang)? I assume they are

Re: [HelenOS-devel] What is wrong with restrict parameters?

On 15 November 2017 at 16:36, Jakub Jermář wrote: > Hi Jiri, > > On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote: >>> Out of curiosity, which C89-only code is being compiled against libposix? >>> >> >> libuv compiles as C89. It would probably work just fine as C99, but as >>

Re: [HelenOS-devel] What is wrong with restrict parameters?

On 11/15/2017 04:43 PM, Jiří Zárevúcky wrote: > On 15 November 2017 at 16:36, Jakub Jermář wrote: >> On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote: Out of curiosity, which C89-only code is being compiled against libposix? >>> >>> libuv compiles as C89. It would probably

Re: [HelenOS-devel] What is wrong with restrict parameters?

Hi, strictly speaking, couldn't you define "restrict" a macro in the same way then? ;) OH On 15.11., Jiří Zárevúcky wrote: > Hi, > > the reason is that "restrict" wasn't a keyword before C99, so those headers > couldn't be included in code written for C89. __restrict__ is non-standard, > but

Re: [HelenOS-devel] What is wrong with restrict parameters?

On Nov 15, 2017 15:20, "Ondřej Hlavatý" wrote: Hi, strictly speaking, couldn't you define "restrict" a macro in the same way then? ;) You couldn't. "restrict" is a legal identifier in C89, and existing code can use it e.g. as a regular variable/function name. Identifiers

Re: [HelenOS-devel] What is wrong with restrict parameters?

Hi, the reason is that "restrict" wasn't a keyword before C99, so those headers couldn't be included in code written for C89. __restrict__ is non-standard, but that doesn't limit its usability in any way -- if you want to use a compiler that doesn't support it, you can just define __restrict__ to

Re: [HelenOS-devel] What is wrong with restrict parameters?

On 15 November 2017 at 15:59, Vojtech Horky wrote: > 2017-11-15 15:49 GMT+01:00 Jiří Zárevúcky : >> On Nov 15, 2017 15:20, "Ondřej Hlavatý" wrote: >>> strictly speaking, couldn't you define "restrict" a macro in the same >>>

Re: [HelenOS-devel] What is wrong with restrict parameters?

Hi Jiri, On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote: >> Out of curiosity, which C89-only code is being compiled against libposix? >> > > libuv compiles as C89. It would probably work just fine as C99, but as > restrict > shows, compatibility between different C revisions is not a 100% thing,

Re: [HelenOS-devel] What is wrong with restrict parameters?

On 15 November 2017 at 17:09, Jakub Jermář wrote: > On 11/15/2017 04:43 PM, Jiří Zárevúcky wrote: >> On 15 November 2017 at 16:36, Jakub Jermář wrote: >>> On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote: > Out of curiosity, which C89-only code is being compiled