Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c > #129780 > unrolled thread

Defect Report Summary for C11 Version 1.12

Back to article view | Back to comp.lang.c

Contents

  Defect Report Summary for C11 Version 1.12 Thiago Adams <thiago.adams@gmail.com> - 2018-04-26 04:05 -0700
    Re: Defect Report Summary for C11 Version 1.12 Keith Thompson <kst-u@mib.org> - 2018-04-26 07:35 -0700
      Re: Defect Report Summary for C11 Version 1.12 Thiago Adams <thiago.adams@gmail.com> - 2018-04-26 10:05 -0700
        Re: Defect Report Summary for C11 Version 1.12 Keith Thompson <kst-u@mib.org> - 2018-04-26 10:35 -0700
    Re: Defect Report Summary for C11 Version 1.12 supercat@casperkitty.com - 2018-04-26 09:09 -0700
    Re: Defect Report Summary for C11 Version 1.12 Philipp Klaus Krause <pkk@spth.de> - 2018-04-26 19:12 +0200
      Re: Defect Report Summary for C11 Version 1.12 Philipp Klaus Krause <pkk@spth.de> - 2018-05-16 08:57 +0200
        Re: Defect Report Summary for C11 Version 1.12 Steve Carroll <frelwizzen@gmail.com> - 2018-05-16 06:38 -0700

#129780 — Defect Report Summary for C11 Version 1.12

This list is interesting because it shows what problems are
being addressed by the C standard.

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm

I think some of these problems were already discussed here.

(I didn't find anything about _func__)

[toc] | [next] | [standalone]

#129792

Thiago Adams <thiago.adams@gmail.com> writes:
> This list is interesting because it shows what problems are
> being addressed by the C standard.
>
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm
>
> I think some of these problems were already discussed here.
>
> (I didn't find anything about _func__)

Why would it mention __func__?  That feature was introduced in C99, and
I'm not aware of any particular problems with it.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#129806

On Thursday, April 26, 2018 at 11:35:37 AM UTC-3, Keith Thompson wrote:
> Thiago Adams writes:
> > This list is interesting because it shows what problems are
> > being addressed by the C standard.
> >
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm
> >
> > I think some of these problems were already discussed here.
> >
> > (I didn't find anything about _func__)
> 
> Why would it mention __func__?  That feature was introduced in C99, and
> I'm not aware of any particular problems with it.

I thought Bart had found (gcc_centric C code) some incompatibilities
that could be caused by lack of clarification of _func_.

[toc] | [prev] | [next] | [standalone]

#129810

Thiago Adams <thiago.adams@gmail.com> writes:
> On Thursday, April 26, 2018 at 11:35:37 AM UTC-3, Keith Thompson wrote:
>> Thiago Adams writes:
>> > This list is interesting because it shows what problems are
>> > being addressed by the C standard.
>> >
>> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm
>> >
>> > I think some of these problems were already discussed here.
>> >
>> > (I didn't find anything about _func__)
>> 
>> Why would it mention __func__?  That feature was introduced in C99, and
>> I'm not aware of any particular problems with it.
>
> I thought Bart had found (gcc_centric C code) some incompatibilities
> that could be caused by lack of clarification of _func_.

Not really.  __func__ was introduced in C99.  bart probably invoked
the compiler(s) in some pre-C99 mode.  (He also had trouble finding
it in the standard.)

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Working, but not speaking, for JetHead Development, Inc.
"We must do something.  This is something.  Therefore, we must do this."
    -- Antony Jay and Jonathan Lynn, "Yes Minister"

[toc] | [prev] | [next] | [standalone]

#129799

On Thursday, April 26, 2018 at 6:05:34 AM UTC-5, Thiago Adams wrote:
> This list is interesting because it shows what problems are
> being addressed by the C standard.

I wonder if the Standard will ever specify any cases where a derived lvalue
or pointer of non-character type can be used to access the storage of the
parent object? I suppose doing so would be a major enough change that it
shouldn't be expected in a corrigendum, but it would nonetheless be nothing
more than the correction of a defect which has been apparent for over 25
years, and has probably caused more trouble than any other.

If the use of derived lvalues was treated as permissible in "obvious" cases,
and if programmers and compiler writers agreed which cases should qualify,
there would be no problem, but it's quite apparent that programmers and
compiler writers have different and incompatible ideas on that subject.

[toc] | [prev] | [next] | [standalone]

#129807

Am 26.04.2018 um 13:05 schrieb Thiago Adams:
> 
> This list is interesting because it shows what problems are
> being addressed by the C standard.
> 
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2148.htm
> 
> I think some of these problems were already discussed here.
> 
> (I didn't find anything about _func__)
> 

There is a more current version from two days ago:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2244.htm

And a separate document for some floating-point issues:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2242.htm

Philipp

[toc] | [prev] | [next] | [standalone]

#130644

Am 26.04.2018 um 19:12 schrieb Philipp Klaus Krause:
> 
> There is a more current version from two days ago:
> 
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2244.htm
> 
> And a separate document for some floating-point issues:
> 
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2242.htm
> 
> Philipp
> 

And another update today (1.14):

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2257.htm

The floating-point-extension version (1.4) is at:

http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2256.htm

Philipp

[toc] | [prev] | [next] | [standalone]

#130647

On Tuesday, May 15, 2018 at 11:57:36 PM UTC-7, Philipp Klaus Krause wrote:
> Am 26.04.2018 um 19:12 schrieb Philipp Klaus Krause:
> > 
> > There is a more current version from two days ago:
> > 
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2244.htm
> > 
> > And a separate document for some floating-point issues:
> > 
> > http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2242.htm
> > 
> > Philipp
> > 
> 
> And another update today (1.14):
> 
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2257.htm
> 
> The floating-point-extension version (1.4) is at:
> 
> http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2256.htm
> 
> Philipp



Recently I did work on and showed some Swift for the front end (only works on Wayland) which is the only thing you can do when trying to avoid nospam's narcissistic crap while reading with Google Groups. 

Idiot. 

I'm getting false positives in my kill filter. I'm guessing the small-minded whackadoodle is unable to control his own actions. My killfiles have him/her/it completely shut out. nospam is incontrovertibly lying, he got caught and he's doing the expected defensive nonsense covered in https://goo.gl/k5FDFL as he busts a gut to keep his story... but it will fail. 



--
Best CMS Solution of 2017!
http://alt.conspiracy.narkive.com/QcWYJ4Px/the-mentally-ill-mark-s-bilk
https://youtu.be/0ZNxaaKD7-c
https://youtu.be/HHT9SJgYsH4
Jonas Eklundh Communication

[toc] | [prev] | [standalone]

Back to top | Article view | comp.lang.c

csiph-web