Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
General Discussion / Re: C2x
« Last post by bas on December 16, 2018, 10:56:47 AM »
Importing these changes will take careful consideration. Many changes however only become relevant when we generate IR code and not C code.
This goes (I think) for 1, 3

2. TBD
4. C2 has an extensible attribute system already, so this is pretty much solved
5. I don't see this ever happening in C also
6. agreed, will be included in C2's macro system partly also.
7. UTF-8 discussion are on the forum, but not really pressing in the current phase.
62
General Discussion / Re: Overwriting fields in init struct.
« Last post by bas on December 16, 2018, 10:51:20 AM »
I'll have to think about this.. I've put in on the Wiki Roadmap so we don't forget.

I did some searching in the kernel code, but couldn't find actual usages. I've done quite some kernel work also
and never actually saw this in use.
63
Ideas / Re: Non-mixing of types bool and integer
« Last post by lerno on December 10, 2018, 11:51:51 AM »
This is one of the core pillars of C flexibility. How many times have you been helped / hindered by this?
64
Ideas / deleted
« Last post by acbaile on December 10, 2018, 01:30:16 AM »
deleted
65
Ideas / Re: Macros again
« Last post by lerno on December 10, 2018, 12:45:46 AM »
Another C type lang with semantic macros worth looking at: http://zl-lang.org/zl-dissertation-univf.pdf
66
Ideas / Re: typedef struct name_ {} name;
« Last post by lerno on December 07, 2018, 06:23:48 PM »
Yes, that works in C2.

On a completely different note: please change the special font you're using. It makes your texts quite unreadable.
67
General Discussion / Re: C2x
« Last post by lerno on December 07, 2018, 06:22:33 PM »
1. Follow the changes here: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2257.htm#dr_476. Volatile should apply to the access of an object through an lvalue marked volatile.

2. Issues supporting u128, i128, u256, i256 should be considered so that C2 doesn't end up with the same problems. Also, consider emulated 128, 256 integer, and a way for supporting optional integers above width of 64 bits http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2303.pdf

3. Issues with atomics that have different guarantees for ++x and x++: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1955.htm

4. User defined attributes: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2269.pdf This could be useful in a macro system, where one could – for example – create a serialization system based on macros and these user defined attributes.

5. "Add a new calling conventions with error return for library functions that avoids the use of errno" relevant for updated error handling in C2.

6. "constexpr to evaluate expressions at compile time as in C++" relevant for semantic macros.

7. Introduce UTF-8 character type: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2231.htm

Some of these are mostly relevant when compiling to LLVM since it affects LLVM code generation.
68
Ideas / deleted
« Last post by acbaile on December 07, 2018, 06:15:11 PM »
deleted
69
General Discussion / Re: Overwriting fields in init struct.
« Last post by lerno on December 07, 2018, 11:05:24 AM »
I am concerned over the fact that we're excluding an important feature that's used in the linux kernel. I would actually claim that we're *not* adding much complexity, since we can actually prune this in the parsing step already!
70
Ideas / Re: Error handling [proposal]
« Last post by lerno on December 07, 2018, 10:49:58 AM »
I understand the scepticism. But let’s see if we can refine the proposal syntax wise first? I’ll adress the practical issues if we can create something syntactically simple.
Pages: 1 ... 5 6 [7] 8 9 10