[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: map.el and naming
From: |
Artur Malabarba |
Subject: |
Re: map.el and naming |
Date: |
Mon, 2 Mar 2015 15:08:07 +0000 |
> I asked whether it would make sense to have the same APIs for both
> groups, and where just the type of the object provides enough
> information for choosing how to process it.
Sorry for being so roundabout. I think the answer here is just "no"
because there are no `plist' or `alist' object type (and there is no
foolproof way of determining whether a given list is intended as a
plist or not).
- Re: map.el and naming, Stefan Monnier, 2015/03/02
- Re: map.el and naming, Stefan Monnier, 2015/03/02
- Re: map.el and naming, Nicolas Petton, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming, Nicolas Petton, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming, Artur Malabarba, 2015/03/02
- Re: map.el and naming, Eli Zaretskii, 2015/03/02
- Re: map.el and naming,
Artur Malabarba <=
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/02
- Re: map.el and naming, Stefan Monnier, 2015/03/02
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/02
- Re: map.el and naming, Stefan Monnier, 2015/03/03
- Re: map.el and naming, Stephen J. Turnbull, 2015/03/03
Re: map.el and naming, bburns.km, 2015/03/03