Subject: Your 100.00 Inside - Goes a long way at Jet Blue

From: Redeem e-Gift Card <[email-masked]>
Date: Wed, 25 Jun 2014 11:14:42 -0700

Hello Atompub-archive, 

Staying in is Out. Enjoy the outdoors in The Palm Beaches, Oceans and Lakes. 

** Special Offer **
- Give Your Opinion and Redeem Voucher that can be used at Jet Blue. 

Enjoy Your $100 Credit -> http://www.dudthat.com/rewards/jetblue/redeem.index
Issued 06/25/2014
RefId# 63-939353

[ Fly from New York to Hilton Head for $101 :: View Similar Deals Below]
http://www.dudthat.com/rewards/jetblue/redeem.index

To stop Further messages - write Current Update Alerts
1644 Doral Dr_Brookings, SD 57006 or visit http://www.dudthat.com/4otj/kr4.4kr4o3d

 To explain things that may not be obvious, or whatever else one might do with comments. I for one often have comments in data files. XML, ini files, and many other formats include provisions for comments.   Michael Burr Oct 28 '08 at 20:51
15	  	
@StingyJack -- I have a key algorithm for my product that must be implemented in three separate languages: Javascript, Objective-C, and Python. A lot of this algorithm can be abstracted away into configuration. And what configuration syntax turns out to be easiest for me to consume in all three cases? JSON, of course. But I'd love to be able to document and comment directly in the configuration files. I realize JSON was originally intended strictly for interchange... but like all things, its use cases grow...   Dave Peck Aug 3 '09 at 23:57
13	  	
Note that where your JSON ends up going is a big part of whether you can or can't comment it. If it's for configuration, then it's likely that you have control over all the parsers that will read it. Since a JSON parser is an extremely simple creature, extending one to allow comments should be very simple. Alternatively, you could use a YAML parser, and YAML does allow comments. (In some ways YAML is a lot more flexible for configuration purposes anyway.)   Pointy Jun 30 '10 at 14:08
  	  	
If you, like me, were wondering whether //comments are OK for the specific use-case of a Sublime Text configuration file, the answer is yes (as of version 2). Sublime Text will not complain about it, at least, whereas it will complain about  the console, because it is an unexpected field.   seafangs Feb 1 '13 at 15:12 @Peter Ajtai - No, it's a comment for the file or transmission, not for any particular part of it. If you put it in Glossary, it would be a comment in the glossary as part of the data, which is exactly what you're trying to avoid.   
  	  	
This works only if you have a comment about a specific object, it doesn't work if you want to comment on a primitive, or if you just want to comment on sections like "plugins here", "model classes here", "controllers am very much aware of the specification and process; in all likelihood I know much, much more about JSON than you do, not j, and participant of json specification forums. But instead of arguing over exact poll numbers (which neither of us has), perhaps you can try arguing WHY comments make no sense? I honestly don't see why any structured textual data format would not have those. But perhaps you can convince me otherwise. Also, FWIW, yes JSON spec is STILL pretty much exactly what Doug wrote. Single person. 
@StaxMan: I stopped reading at in all likelihood I know much, much more about JSON than you do. Are you actually serious? I don't recall ever sending you my CV. But if you feel the need to resort to this sort of baseless, arrogant rhetoric then you are clearly already beyond the capacity for any sort of productive  and you, on the other hand, have offered no arguments for excluding comments in JSON; or why you think that there is significant portion of developers who like things that way. At most I can 
The reason presented for comment removal by Doug C is pretty trite. If I were to remove all the features of C or Javascript that are routinely abused by self-proclaimed 'clever' programmers, I wouldn't have anything left to work with. And if using comments to optionally 'extend' the functionality of the JSON syntax is not allowed, what is it if I just (inefficiently) embed the same parameters into the JSON itself? I could easily write some JSON and embed parsing directives into the JSON syntax itself (in the form of "object values"). Is that any more or less interoperable than comments?   jstine Feb 26 at 17:05
Many/most JSON libs support comments, because comments really SHOULD be part of JSON spec -- everyone except JSON author agrees here. And comments are hardly only for manual-editing; they are great for notes on config files, but also good when machines generate data files, including dev-debuggable metadata (creation time etc). In fact, pretty much the same reasons why XML/HTML have comments.   StaxMan May 8 '13 at 21:51