4 ms·

You are invited to bring forward concrete proposals for changes to the C standard in the relevant committee. http://www.open-std.org/jtc1/sc22/wg14/ http://www

by jpfr 8y ago

You are invited to bring forward concrete proposals for changes to the C standard in the relevant committee. http://www.open-std.org/jtc1/sc22/wg14/ http://www.open-std.org/jtc1/sc22/wg14/ Since UB allows the compiler to do anything in those situations, we can reduce the amount of UB without breaking existing “legal” code. By actually defining more behavior. If a proposal is reasonable needs to be discussed in the standardization committee. All other discussions are a nice hobby. But eventually moot.

vyodaiken 8y ago
I will.
wolfgke 8y ago
> You are invited to bring forward concrete proposals for changes to the C standard in the relevant committee. My proposal: make the future versions of the C standard freely available (not only drafts).
xorblurb 8y ago
Those kind of discussions have various effects, some of which I believe to be far from moot. First, they permit that some people even take notice about this situation. Few developers read the standard and even less write it or follow the discussions to change it (are they even open?) or write a compiler for it. The rationales are not even tracked [1]. It actually would be insanely hard to get a good understanding of those subjects by e.g. just reading the standard, without having those kind of discussions on forums typically used by more devs than just a few dozens of compiler writers... [1]: but while I'm thinking about it, an impressive independent book as been written by Derek Jones: The New C Standard: An Economic and Cultural Commentary http://www.knosof.co.uk/cbook/cbook.html http://www.knosof.co.uk/cbook/cbook.html
vyodaiken 8y ago
Here is a start. https://docs.google.com/document/d/1xouelPcphQ-o7DmdSwz5UcL42M6bdA3t93Nm_5Hbomc/edit?usp=sharing https://docs.google.com/document/d/1xouelPcphQ-o7DmdSwz5UcL4...
- jpfr 8y ago
  If desired, I can comment your document over a private channel. In that case, please give a short heads-up when ready. Note that I am not directly affiliated with WG14. So take my comments with a grain of salt.
  - vyodaiken 8y ago
    i think you should be able to make private comments on that document. Otherwise victor.yodaiken@gmail.com

by jpfr 8y ago

vyodaiken 8y ago

I will.

wolfgke 8y ago

> You are invited to bring forward concrete proposals for changes to the C standard in the relevant committee. My proposal: make the future versions of the C standard freely available (not only drafts).

xorblurb 8y ago

Those kind of discussions have various effects, some of which I believe to be far from moot. First, they permit that some people even take notice about this situation. Few developers read the standard and even less write it or follow the discussions to change it (are they even open?) or write a compiler for it. The rationales are not even tracked [1]. It actually would be insanely hard to get a good understanding of those subjects by e.g. just reading the standard, without having those kind of discussions on forums typically used by more devs than just a few dozens of compiler writers... [1]: but while I'm thinking about it, an impressive independent book as been written by Derek Jones: The New C Standard: An Economic and Cultural Commentary http://www.knosof.co.uk/cbook/cbook.html http://www.knosof.co.uk/cbook/cbook.html

vyodaiken 8y ago

Here is a start. https://docs.google.com/document/d/1xouelPcphQ-o7DmdSwz5UcL42M6bdA3t93Nm_5Hbomc/edit?usp=sharing https://docs.google.com/document/d/1xouelPcphQ-o7DmdSwz5UcL4...

jpfr 8y ago
If desired, I can comment your document over a private channel. In that case, please give a short heads-up when ready. Note that I am not directly affiliated with WG14. So take my comments with a grain of salt.
- vyodaiken 8y ago
  i think you should be able to make private comments on that document. Otherwise victor.yodaiken@gmail.com