This project has moved and is read-only. For the latest updates, please go here.

Parse, interpret, patch and writeback?

Nov 1, 2011 at 9:57 AM


Is there any concern against using Irony to create/alter the file on the specified format?

Our system is using a lot of various config files, and it would be nice for the .NET toolchain to have the format specified in just one place. For the whole CRUD on details within the parse tree.

Is the code that I would use for new'ing up the "parse tree" anywhere near as fluent as the code for grammar specification? Property initializers? Collection initializers?

Nov 1, 2011 at 7:02 PM

Sorry, don't understand at all what do you mean. Can you please be more specific, maybe provide an example, end-to-end scenario with "formatted config" snippets?



Nov 1, 2011 at 7:35 PM


Could you show an example on how you would, for example, create a JSON object from code that would be possible to output to file/stream using the JSON specification in Irony?

Nov 2, 2011 at 5:29 PM

there's some misunderstanding I guess. Irony's sample grammar for JSon allows you to PARSE json files - to convert from text stream into parse tree that you see on the right in grammar explorer. It does not provide you with reverse operation - from object to Json. 


Nov 2, 2011 at 8:51 PM

Ok. Thank you.

Of course, it would be cool if you could use the same Irony file format specification regardless of wether you intented to

  • read,
  • create
  • read->update->write.

ORM to any format, if you will.

Thank you again. The code for specifying format is nice and crisp.