6 Commits (ccf19fbf5e2b61ba62efd1ac47a3a3fd3917d494)

Author	SHA1	Message	Date
Martin Atkins	1dc4950bfa	lang/funcs: Rename the base64 character encoding functions ... These were initially introduced as functions with "encode" and "decode" prefixes, but that doesn't match with our existing convention of putting the encoding format first so that the encode and decode functions will group together in a alphabetically-ordered function list. "text" is not really a defined serialization format, but it's a short word that hopefully represents well enough what these functions are aiming to encode and decode, while being consistent with existing functions like jsonencode/jsondecode, yamlencode/yamldecode, etc. The "base64" at the end here is less convincing because there is precedent for that modifier to appear both at the beginning and the end in our existing function names. I chose to put it at the end here because that seems to be our emergent convention for situations where the base64 encoding is a sort of secondary modifier alongside the primary purpose of the function, as we see with "filebase64". (base64gzip is an exception here, but it seems outvoted by the others.)	6 years ago
r0bnet	877399c631	lang/funcs: Functions for encoding text in specific character encodings	6 years ago
Kristin Laemmert	6171ba3b8a	base64decodeFunc now checks for valid UTF-8	8 years ago
Kristin Laemmert	eb1d8b7909	cleanup comments for nicer godocs	8 years ago
Kristin Laemmert	1a5299efcb	porting encoding functions	8 years ago
Kristin Laemmert	d4e703a5c1	base64decode	8 years ago