I didn't think to enumerators... Yes, #delete_at is a better choice than #delete, didn't think to it neither... But #delete and #delete_if methods seem to not call #delete_at neither. Please let me reword the proposal: may #delete ...sdaubert (Sylvain Daubert)
When a class inherits from Array, and its #delete methods is modified, #delete_if and #reject! do not call this method. From sources, its an internal C method which is called instead. Is there a way to modify #delete_if and #reject! t...sdaubert (Sylvain Daubert)
* ext/digest/digest.c: - remove HMAC from list of digest algorithms, - add MD5 in list of digest algorithms, - add information about writing a C digest implementation using Digest::Base, - add documentation for Digest::B...sdaubert (Sylvain Daubert)
trans (Thomas Sawyer) wrote: > Why keep the source code in the Ruby repository at all? Development occurs at the library's repository anyway, so why waste time with copying the files into Ruby repository for each release. Instead, just ...sdaubert (Sylvain Daubert)
Improve Regexp documentation: * add a section to explain differences between =~ operator and #match * in Options section, explain how use options with Regexp.new * add a section about special global variables ($~ and so on)sdaubert (Sylvain Daubert)
sdaubert (Sylvain Daubert)06:32 PM Ruby Feature #14887: Array#delete_if does not use #delete