From: Oren Ben-K. <or...@ri...> - 2001-11-27 07:11:41
|
Clark C . Evans [mailto:cc...@cl...] wrote: > Comments: > > - Do !map and !seq in-line forms do implicit > typing on their contents... they should. Hmmm. I see why you'd want it. Note this means that a transfer method has the power to recursively invoke the "implicit transfer" mechanism, which in turns invokes other transfer methods - so this complicates the APIs. I guess it makes sense to allow for it... I'm (gulp) OK with adding it. YADN (Yet Another Disruptive Noise :-): Time keys are ugly. ? \ 14:30 : Meeting Quoting the key doesn't help (because quoted scalars are a form of plain scalar). Alternatives: - Keep it that way. Plus: no work. Minus: keys with ':' (such as dates) would look ugly. - Make quoted keys a full-blown scalar style. Plus: allows the most general form of in-line keys. Minus: complicates spec(?) - Exchange ':' and '=': Example: map = key = value 14:30 = meeting ptr = !ptr := value Plus = - using '=' is the way people write configuration files today. - Using '=' looks better for scalar values. - ':= value' for default value of a map is much better compared to '=:' which we have today. - Plain scalar keys are less likely to contain '=' than ':'. Minus = - Using ':' looks better for collection values. - We got used to ':' ... Thoughts? Have fun, Oren Ben-Kiki |