Karsten,
Fair enough, as I mentioned to Travis in our offline follow-up, I had solved my problem with the API by adding the following,
UserMessage>>exists
^(Locale current lookUp: self) ~~ nil.
So now I can iterate over user messages and check their resolution without having to use #asString and checking its return value, which is what was getting in the way originally.
Thanks!
-Boris
--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4[hidden email]
CONFIDENTIALITY NOTICE
This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.
Thank you.
> -----Original Message-----
> From: Karsten [mailto:
[hidden email]]
> Sent: Wednesday, August 20, 2008 2:21 PM
> To: Boris Popov
> Cc: VWNC
> Subject: Re: [vwnc] Default user message resolution question
>
> Hi Boris,
>
> i guess the idea is to provide at least some text instead of no text at
> all. And as the key is typically not just a number but a somewhat
> meaningful string, this key is just returned.
>
> Kind Regards
> Karsten
>
>
>
> Boris Popov wrote:
> > What is the rationale for having user messages return their key if
> > default isn't provided and key wasn't found in the catalog?
> >
> > (#SimpleQ << #catalog) asString -> 'SimpleQ'
> >
> > -Boris
> >
> >
>
> --
> Karsten Kusche - Dipl.Inf. -
[hidden email]
> Tel: +49 3496 21 43 29
> Georg Heeg eK - Köthen
> Handelsregister: Amtsgericht Dortmund A 12812
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc