Re: ver. 4.0 std include files type conflict
- Posted by jeremy (admin) Mar 18, 2009
- 855 views
That's true, but I think this is adding confusion as to the type of map we're dealing with. I haven't really looked at sets.e previously, so I'm not familiar with it. While we define multiple routines that do similar things to different types of data, here we're talking about different types of data.
Looking at the documentation that's there, a sets:map appears to be a sequence of indices that define the permutation to make sequence s1 into sequence s2. So it's true that it 'maps' between the two sequences, but maybe not the most appropriate name.
Guess I was too quick on this one, I have not looked at sets either.
I think this particular instance is a good catch by Bernie. Here are some suggestions that come quickly to mind:
- permutation
- index_map
- translation
Namespaces work for types as well and I do not see a problem with that, however, there is no reason to have a conflict because something is named incorrectly, or a better name exists for one of them. The above suggestions for changing set, also map.e is frequently called a dictionary, or dict. I am unsure of what is the most common word for what we have in map.e.
Jeremy
