Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.os.vms    |    DEC's VAX* line of computers & VMS.    |    264,096 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 262,831 of 264,096    |
|    =?UTF-8?Q?Arne_Vajh=C3=B8j?= to Lawrence D'Oliveiro    |
|    Re: VMS x86-64 database server    |
|    10 Jul 25 19:05:42    |
      From: arne@vajhoej.dk              On 7/10/2025 12:28 AM, Lawrence D'Oliveiro wrote:       > On Wed, 9 Jul 2025 22:24:50 -0400, Arne Vajhøj wrote:       >> There are fundamentally two different ways of handling errors:       >> * return status       >> * exception       >       > There’s a difference between different statuses that might be returned as       > part of the normal execution of an operation, and unexpected conditions       > indicating program bugs.       >       > Syntax errors in the embedded language would almost always belong in the       > latter category.              Yes.              Java operate with checked and unchecked exceptions based on       that logic.              But I don't see any point for the problem at hand.              If the PHP developer configure the database connection       to not throw exceptions because the developer want to       check return status, then that must be respected. It       does not make any sense of the database extension is       is coded like "SQL syntax is so serious a bug, so even       though the developer asked me not to throw exceptions, then       I will throw one anyway". The code is not prepared to       handle exceptions, because the developer expect the       driver to throw one when told not to.              Arne              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca