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

Andrey Somov <[email protected]> Wed, 2 Mar 2016 18:08:32 +0100
Newsgroups gmane.text.yaml.general
Message-ID <CALbkv0fp1wan5U25jnqYmOqCo4ph63hFNjXgfmn1WfqaYGFRVA@mail.gmail.com>
If no one knows what is "Clip Block Chomping Indicator", then using it is a
mistake. You can always find a work around.
You can also say - just use a subset of YAML and do not bother about "Clip
Block Chomping Indicator".

Andrey







On Wed, Mar 2, 2016 at 5:32 PM, Felix Krause <[email protected]> wrote:

>
> > On 02.03.2016, at 17:09, Andrey Somov <[email protected]> wrote:
> >
> > >On the contrary: Complex objects (structs, records, classes, tuples,
> however they are named) are part of most programming languages, and it is
> fine to use them as mapping keys. So YAML should support them (see my other
> answer for an example).
> >
> > If something is possible to do it does not mean it should be done.
>
> Since you have been shown that there are lots of use-cases for complex
> keys, you have yet to provide a reason why the feature should be removed.
>
> >
> > >Firstly, YAML was designed as a serialization language.
> > If YAML is used primarily as configuration should it reflect the reality
> and adapt ?
>
> So, consequentially, you want to remove anchors/aliases and tags from
> YAML? They are not really useful for configuration files and I have never
> seen them being used in one.
>
> As I see it, configuration files tend to use a subset of YAML. Which is
> fine. But what would be the reason to restrict YAML to that subset?
>
> > >Secondly, allowing this argument would create a chicken-and-egg-problem
> > There is no problem. Complex keys were introduced many years ago and
> they are not used.
> > No one showed still ANY live example of complex keys.
>
> So you deduce from not getting an answer from a mailing list within a few
> hours, that a feature is never used and may safely be removed?
>
> I can tell you that my YAML library uses complex keys when dumping native
> data structures, as probably other libraries do if they implement
> serialization of native data types. But as I said earlier, in the case of
> serialization YAML is not necessarily visible to the user.
>
> If you are so eager to remove the feature, please tell me how you would
> represent a mapping which has complex numbers as keys. What would be your
> alternative?
>
> Cheers,
> Felix

------------------------------------------------------------------------------
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