• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: in-class initialization of fundamental types
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: in-class initialization of fundamental types


  • Subject: Re: in-class initialization of fundamental types
  • From: Jerry Krinock <email@hidden>
  • Date: Fri, 23 Sep 2005 15:38:51 -0700

on 05/09/23 15:23, Markian Hlynka at email@hidden wrote:

> Isn't the following suppposed to be legal in c++?
>
> class foo
> {
>      public:
>          static const int foo_max_size = 100;
>
>      private:
>          char fooname[foo_max_size];
> };
>
> xcode (and thus gcc4) doesn't seem to allow it, but I was certain I'd
> read somewhere that this was now legal??

I didn't think so, but to my surprise I pasted your declaration into a .mm
file in my CodeWarrior Objective-C++ project and CodeWarrior compiled it
without complaint.  For what it's worth.


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: in-class initialization of fundamental types
      • From: Markian Hlynka <email@hidden>
References: 
 >in-class initialization of fundamental types (From: Markian Hlynka <email@hidden>)

  • Prev by Date: in-class initialization of fundamental types
  • Next by Date: Specifying "enum" data size
  • Previous by thread: in-class initialization of fundamental types
  • Next by thread: Re: in-class initialization of fundamental types
  • Index(es):
    • Date
    • Thread