Imho, choose based on what makes the implementation better. If the parser can be written in a simpler (and probably faster) way by dropping support for ratios in uncommon bases, then let's do it. Tbh, I don't think any ratios other than those on the format int1/int2 needs to be supported.
2016-10-24 19:23 GMT+02:00 Jon Harper <jon.harpe...@gmail.com>: > Hi list, > I'm reading the questions at https://github.com/factor/factor/pull/1362 > again > > I think we should only allow ratio literals in base 10. Currently we support > 0xc+b/a or 0o4+7/3 or 0b1101+1101/110 but it looks ugly. > > What do you think ? > > Jon > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Factor-talk mailing list > Factor-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/factor-talk > -- mvh/best regards Björn Lindqvist ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ Factor-talk mailing list Factor-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/factor-talk
