Naming collision between Processing `map()` and Python `map()`

[SableRaf]

Trying to port the array example (See issue: Port Basics / Arrays / Array #3) and I'm running into this error:

coswave = [abs(cos(map(i, 0, width, 0, pi))) for i in range(width)]
                       ~~~^^^^^^^^^^^^^^^^^^^^
TypeError: 'int' object is not iterable

I suppose this is because Python has its own map() function (a list transformation) different from the map() function in Processing (a linear interpolation function).

Processing.py handles this by wrapping map() and dispatching based on the arguments (see source code). It uses the Processing version when called with five numeric arguments, and otherwise falls back to Python’s built-in. Note: the same approach is used for filter().

By contrast, py5 avoids the conflict by renaming the function to remap() instead.

[hx2A]

py5 also replaces filter() with apply_filter(). Other Processing functions like abs() that would create a conflict are left out entirely because Python provides that natively.

I didn't like the idea of wrapping the builtin functions because I thought it might confuse beginners a bit because it blurs the line between builtin functions and py5 functions. Also, I wanted to have "reserved words" that could be given a different color for syntax highlighting.

That logic doesn't apply cleanly to libprocessing because libprocessing will support a variety languages. If you rename something for one language, do you rename it for all of them? What if one language would benefit from providing an abs() function but another does not? How strictly consistent should the variable and method names be across the various languages? What happens if you want to support a new language down the road?