• 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: //Comments
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: //Comments


  • Subject: Re: //Comments
  • From: Philip Aker <email@hidden>
  • Date: Wed, 14 Jan 2009 19:26:17 -0800

On 2009-01-14, at 17:32:58, Gil Dawson wrote:

The only C standard I had to point to was the K&R book, and I was reluctant to use any extensions.
I at first thought that // was in K&R, so I used // until some error having to do with #define made me go look.

Now I can use // with confidence so long as the selected microcontroller's compiler complies with

WG14/N1124 Committee Draft — May 6, 2005 ISO/IEC 9899:TC2

Is this the same as the "C99 Standard"?

Effectively yes. If you avoid the edge cases mentioned in section 6.4.9 you'll not have any problems with a conforming compiler. It specifically mentions a case using a macro to define a // comment.


Otherwise, any normal code editor can mass replace C++ comments with C comments very quickly.


Philip Aker echo email@hidden@nl | tr a-z@. p-za-o.@

Democracy: Two wolves and a sheep voting on lunch.

_______________________________________________
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


References: 
 >//Comments (From: Gil Dawson <email@hidden>)
 >Re: //Comments (From: Fritz Anderson <email@hidden>)
 >Re: //Comments (From: Gil Dawson <email@hidden>)

  • Prev by Date: Re: Xcode Goes Into Debugger Without Breakpoint or Error
  • Next by Date: Inline errors on XCode 3.1.1 and libgmp 4.2.4
  • Previous by thread: Re: //Comments
  • Next by thread: Re: //Comments
  • Index(es):
    • Date
    • Thread