Re: Bit module function names

[Majic <majic.one@...>]

While you're speaking for everyone, Mr. Donnelly, would you care to
explain why bit.or(), bit.and(), bit.xor(), etc... is unacceptable
beyond the impression that no one else wants to see unneeded [""] ?
Also wish they had the usual operators tied to them.. like `something
& something_else' and that you could overload them through a .__band.
In that instance I would see the need for the prefixed b, but Stuart
is right.  Inside the bit table it's a bit strange. (harr harr, pun)

Regards

On Mon, Feb 8, 2010 at 11:35 AM, Patrick Donnelly <batrick@batbytes.com> wrote:
> On Mon, Feb 8, 2010 at 2:04 PM, Stuart P. Bentley <stuart@testtrack4.com> wrote:
>> Isn't it a bit silly/redundant to prefix all of the functions in the 'bit'
>> table with 'b'? After all, the 'string' module functions in the table don't
>> start with 'str'. (I understand the need to distinguish 'and' and 'or' from
>> the keywords, but they usually have a bitwise qualifier in regular speech as
>> well, unlike "bitwise XOR".)
>
> You really want to see bit["or"], bit["and"], etc. in all the code you
> read? (Hint: no one else does :P)
>
> --
> - Patrick Donnelly
>