From: Oren Ben-K. <or...@ri...> - 2001-11-22 07:05:10
|
Brian Ingerson [mailto:in...@tt...] wrote: > 1) What happens if a plain scalar that begins with a non > alpha character does > not match an implicit type. Is it: > > A) An error > B) A warning > C) Silently assumed a string An error. > This should be clearly stated in 2.8.2. Yes. > 2) What is the value of this: > > foo: "bar" > > I assume it's '"bar"'. It is an error. > We should probably warn on this if we > want to reserve quotes for future use. '"' is a reserved indicator and a plain scalar can't start with one. > The accepted form should be: > > foo:\"bar" We have no in-line escaped scalar format. The above is an error. > or > > foo:\ > "bar" Yes. That would work. > 3) Can we do inline forms of folded or escaped? Currently we can't. > I don't see > examples in the > spec. > > escaped:\\ \tfoo > > same as: > > escaped: \\ > \tfoo Not valid today. We've discussed it and decided not to, due to confusion between in-line escaped and in-line folded: escaped: \\ with leading scape folded: \ without leading space block: ||chomped block: | ends with newline Too confusing. Currently every "indicated" scalar type starts at the next line. That seems simple and consistent. BTW, what's the final verdict on '.relative' transfer methods? Have fun, Oren Ben-Kiki |