byte types

[Skaperen]

you're talking more about how things like len() are implemented, which is not something that matters to the programmer (nor should it) while i am talking about how the API design affects the programmer and how she goes about using that design to make use of the facility it describes. if Python did not have a len() function and it had to be user implemented, would you want there to be different function call names depending on the datatype the caller wants to get the length of? i would not. i would describe the API before any implementation is done (although there might be design changes after testing has a test implementation done and it is then discovered that the API design had flaws that needed to be changed or additions would be helpful). consider the clen() function i described in my previous post. what if Python was going to include it in the language? its implementation might well be like how len() is done, calling the __clen__() method in each specific type. but what if, before this, it had been decided to have different names for different types lik lclen() for lists, tclen() for tuples, and baclen() for bytearrays? would you expect to see the name changed because of the way it is implemented? i would not. and this is why i would just call it clen() to begin with.

i do have a couple of functions in my function collection that have type varying names. but their names are based on what type is returned ... bachr() to return one bytearray character from its code number ... and bchr() for bytes type. both accept int as the one argument.

dynamic typing as a language feature seems to be rather lost in Python due to a lot of people effectively saying not to use it. for me, it is one of the great features of Python.