Don't forget with have this: http://felix-lang.org/$/usr/local/lib/felix/felix-latest/share/lib/std/datatype/slice.flx
In principle we could change Slice_range to read Slice_range_inclusive, and add Slice_range_exclusive. Or something. Again it isn't exactly clear what the semantics are. One approach would be to define slice types with the semantics we want, these would then be useable. Then we have two separate problems: 1. inventing some syntax for common cases. 2. optimising it. Using an iterator as in the code above is horribly inefficient. Suitable for a scripting language .. not for high performance numerical work. However we can actually do optimisations based on *syntax* of special cases .. the advantage is that now we have an agreed on semantic model. -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
