On Thu, Mar 15, 2018 at 05:47:41PM -0700, Adam Williamson wrote: > So: there would be no problem with - in the *name* of the modules, so > long as that's the first field, which apparently it is. > > The problem is if you allow the delimiter in *both* the first and last > fields, or in *any other field besides the first and the last*. As soon > as you do that, parsing is impossible. This is the issue with module > names, as Patrick pointed out: they allow - in the stream, which is the > *second* field. As soon as you allow this, reliably parsing the name > components out of the whole name becomes impossible. > > Yes, you can say 'just don't parse strings, go ask a service instead', > but parsing strings is sometimes by a long way the most convenient way > to do things, and I really can't see how allowing the delimiter > character to appear in one of the field names is a *bigger* win than > allowing the components to be reliably parsed from the overall name. I wonder what we can do about this. Is it FESCo material? Can the folks working on modularity comment more on this? This is quite failing the moto: it's ok to disagree, not to surprise Pierre _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
