bdw429s02/10/2022, 5:57 AM
miguel-f02/10/2022, 12:30 PM
Mark Takata (Adobe)02/10/2022, 3:38 PM
It is doing exactly what it was built to do.Yeah but if what it was being built to do is wrong, then it's still a bug. If you write a function called
and it returns
because you specifically decided "we're only using this in the bible, and god's understanding of trigonometry is a bit bronze age", then it's still a bloody bug because it's wrong. "wrong" can be "because it's inappropriately inaccurate (as in here), or "because it's a security vulnerability". Poor design decisions are bugs.
Mark Takata (Adobe)02/10/2022, 7:56 PM
then my entire life is pretty much a bugI think it's important to note that it wasn't me who said that.
Adam, we can go back and forth endlessly on this.And that just sounds like a dare.
bdw429s02/10/2022, 9:49 PM
It is doing exactly what it was built to do.@Mark Takata (Adobe) The docs I linked to in the comments of the ticket clearly state the len() function accepts two things • strings • binary How can you possibly stand by the idea that accepting a UDF is working as designed. It's certainly not working as documented. So at least one of these two simply cannot be correct. You must either update the docs to match the function or the function to match the docs. But they can't be different and us still pretend everything is fine.
Feature request number is: CF-4212752. Feel free to vote it up if you'd likeThat ticket not only has nothing to do with mine, it makes zero sense and it written by someone who has no clue what's going on. Firstly, they think
is an "error" when it's nothing of the sort! It's the name of the class in memory, not an error at all. I have no issues with the fact that certain classes have the ability to represent themselves as a string-- that is wholly unrelated to the input validation of the
Mark Takata (Adobe)02/10/2022, 11:09 PM