On Mon, May 27, 2019 at 09:28:44AM +0200, [email protected] wrote: > > On Sun, May 26, 2019 at 09:05:37PM +0200, [email protected] wrote: > > > > > > > > The attached patch ensures we write such identifiers as |:type-tests:| > > > > regardless of keyword style. This way, it can also be read by any > > > > program, even if it uses a different keyword style than the writer. > > > > > > > > > > Ugh... How ugly. Is there no way around this? The "|" are only necessary > > > in "readable" mode, right? > > > > What do you mean by readable mode? If you mean that it's only needed > > when you want to later use READ to read back the expression, then yes. > > For regular display it doesn't matter. > > Yes, write vs display, that's what I meant.
Yeah, it's only necessary there. > > I don't see how it's a huge problem; one wouldn't need to write such > > symbols very often, and usually you have suffix style enabled, so the > > pipes are only unnecessary when the symbol only starts with a colon. > > When there's a colon on both ends or on the right side, you _have_ to > > pipe-quote it anyway, and we do already. > > It's not a HUGE problem, just ugly. So I understand this only applies to > |:XXX:|? > Then it is a different story... When using "suffix" kw style, it applies to |:xxx| and |:xxx:|. We currently already handle |xxx:| like that, so that won't change. Of course regular symbols without colons at the ends won't need to be quoted! So, something like SRV:send-reply will just be emitted without pipes as well. Cheers, Peter
signature.asc
Description: PGP signature
_______________________________________________ Chicken-hackers mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/chicken-hackers
