Re: YAML 2.0: drop arbitrary nodes to be used as keys

>No. Tuples are immutables in Python, and can be used as keys in Python
dictionaries.

This is exactly the message I would like to prevent.
(background - I used PyYAML a lot, as well as SnakeYAML)

The message: it must be in YAML because it is supported by _my_language_.
It means that YAML ends up with every dirty trick ever invented for any
programming language. Do we want that ?
Do not we suffer now from the result of trying to put any hack to the
specification (1:2 is integer !!!)?
Should we think about inter-operability ?

We should not implement things because it is possible, we should implements
things which are useful.
If we take only one language (regardless which one), then I am off.
(because then YAML is useless for me)

All the public YAML (which I know) does not use complex keys.
- ansible
- google engine
- testNG
- RAML
- polyglot Maven

Can anyone show an example of the public usage of YAML with  a complex key ?

Andrey

------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140

_______________________________________________
Yaml-core mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/yaml-core