Opened 13 years ago

Last modified 13 years ago

#776 new Defect

AS: apparent new class bug in CTCP processing (process subcode)

Reported by: Niteshade Owned by: timothy
Component: Colloquy (Mac) Version: 2.2 (Mac)
Severity: Normal Keywords: Applescript CTCP process subcode request


With a CTCP processing applescript routine that starts with -

on process subcode request mystring with mybug from...."

I get a problem with the data returned for mybug in the latest build (Colloquy 2.1 (3315) - Mac OS X 10.4.6 (PowerPC)).

if I /ctcp (nick) one -- then mybug is missing value (this seems to be something new vs previous versions)

if I /ctcp (nick) one two -- then mybug gets the following errors...

I get coercion errors with mybug.
When I display the class of mybug it gives ""
When I display the class of mybug as text, then it shows the class as "anything".

mybug is supposed to return a string (according to the dictionary) - and this is what it used to do.

mystring's class is returned as unicode text (this is good) - but this is not consistent with the dictionary which says that it's a string.

When I try to coerce mybug to text, the try block error is "Can't make «data 68656C70» into type string"

I didn't have this problem in earlier versions. Has something changed, or have I simply got something odd going on in my system?


Change History (1)

comment:1 Changed 13 years ago by colloquy

Were the parameters changed from string to unicode text (a good thing) in this version?
Perhaps a simple bug crept in?
(also does the dictionary need an update to state that this is unicode text, rather than string?)

PS FWIW the problem is still here in OS 10.4.7

Note: See TracTickets for help on using tickets.