Re: #38337 [Opn->Bgs]: explode function's return value is incorrect

> Many functions return FALSE if something goes wrong/data has been > exhausted/the function does not find what the developer was looking > for. > > In fact, we'd have to mark a great number of functions in the manual > "mixed" if we followed the convention you propose. Instead, we mark > return values as the most common case(s), and avoid error situations. > > See strpos(), each(), mysql_fetch_assoc(), etc. Is this actually in the manual, anywhere? I don't see it... but I know we follow this convention. If so, please tell me where (-: If not, I propose we add something like the above to language.pseudo-types S