Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-02-27 | stdlib: Fix mime_decode/1 binary matching performance | Jesse Stimpson | |
Symptom: Throughput of base64:mime_decode/1 significantly lower than base64:decode/1. Problem: tail_contains_more/2 prevents compiler from delaying creation of sub binaries. Solution: Restructure mime_decode_binary/2 to use binary matching best practices from the Efficiency Guide. See ERL-366 | |||
2016-03-15 | update copyright-year | Henrik Nord | |
2015-06-18 | Change license text to APLv2 | Bruce Yinhe | |
2013-01-25 | Make adjustments for Unicode | Hans Bolinder | |
2013-01-21 | [hipe, kernel, stdlib] Correct a few types | Hans Bolinder | |
The type ascii_string() in the base64 module has been corrected. The type file:file_info() has been cleaned up. The type file:fd() has been made opaque in the documentation. The type nodes() has been removed from erl_bif_types.erl. | |||
2011-05-12 | Types and specifications have been modified and added | Hans Bolinder | |
2011-01-17 | Removed use of deprecated function size | Ingela Anderton Andin | |
2010-12-07 | Improve pad character handling in base64 MIME decoding functions | Thomas O'Dowd | |
Implement the 'MAY' clauses from RFC4648 regarding the pad character to make mime_decode() and mime_decode_to_string() functions more tolerant of badly padded base64. The RFC is quoted below for easy reference. RFC4648 Section 3.3 with reference to MIME decoding: Furthermore, such specifications MAY ignore the pad character, "=", treating it as non-alphabet data, if it is present before the end of the encoded data. If more than the allowed number of pad characters is found at the end of the string (e.g., a base 64 string terminated with "==="), the excess pad characters MAY also be ignored. | |||
2009-11-20 | The R13B03 release.OTP_R13B03 | Erlang/OTP | |