Andreas,
I ran into a warning about LDAPResult>>checkForExceptions sending the now deprecated #or:or:. It was easy to silence (comment out the warning), but that won't fix the problem.
Maybe (untested):
checkForExceptions ( #( 0 5 6 ) includes:resultCode ) ifFalse: [ | ex | ex := LDAPException newWithCode: resultCode. ex signal: (errorMessage ifEmpty:[ex messageText]) ]
Bill
On 7/2/2010 2:31 PM, Schwab,Wilhelm K wrote:
Andreas,
I ran into a warning about LDAPResult>>checkForExceptions sending the now deprecated #or:or:. It was easy to silence (comment out the warning), but that won't fix the problem.
Sorry, I don't understand. There is nothing deprecated about #or:or:.
Cheers, - Andreas
Maybe (untested):
checkForExceptions ( #( 0 5 6 ) includes:resultCode ) ifFalse: [ | ex | ex := LDAPException newWithCode: resultCode. ex signal: (errorMessage ifEmpty:[ex messageText]) ]
Bill
On Fri, 2 Jul 2010, Andreas Raab wrote:
On 7/2/2010 2:31 PM, Schwab,Wilhelm K wrote:
Andreas,
I ran into a warning about LDAPResult>>checkForExceptions sending the now deprecated #or:or:. It was easy to silence (comment out the warning), but that won't fix the problem.
Sorry, I don't understand. There is nothing deprecated about #or:or:.
I think it's deprecated in Pharo 1.1. The easiest way to fix is to use #or: twice. "a or: [ b ] or: [ c ]" simply becomes "a or: [ b or: [ c ] ]".
Levente
Cheers,
- Andreas
Maybe (untested):
checkForExceptions ( #( 0 5 6 ) includes:resultCode ) ifFalse: [ | ex | ex := LDAPException newWithCode: resultCode. ex signal: (errorMessage ifEmpty:[ex messageText]) ]
Bill
squeak-dev@lists.squeakfoundation.org