Sweet16 progress notes
August 06, 2006 at 11:31 AM
I'm working on a new version of Sweet16 that's likely
to be numbered 1.7. I don't have the slightest idea
yet when it'll be done. The main thing it will
include is what I hope will be decent support for
Unicode filenames, which is a major undertaking. This
problem came up quite simply: on BeOS, from which the
code is adapted, the standard C string library
routines (strcpy(), printf(), etc) all used UTF-8
strings, so they were ready to go for non-ASCII
characters. Unfortunately, Mac OS X uses straight
ASCII for those, so I have to recode everything.
I'm in the process of redoing it all to use CFURLRef and CFStringRef objects for the pathnames and filenames. This is taking some seriously tedious work, although it's not all that hard.
I'm doing all my testing in the PowerPC build because Xcode's debugging support for x86 doesn't seem to want to show me the source code -- it all comes up in assembly. Yuck.
I'd like to thank everyone that's emailed the kind messages about how much they like Sweet16 -- even when they have bugs to report as well. That's always nice when folks say, "Hey, even though I've got this problem to report, I'm sure happy you're doing this project." Beats getting chewed out, which I've had happen on other projects...
I'm in the process of redoing it all to use CFURLRef and CFStringRef objects for the pathnames and filenames. This is taking some seriously tedious work, although it's not all that hard.
I'm doing all my testing in the PowerPC build because Xcode's debugging support for x86 doesn't seem to want to show me the source code -- it all comes up in assembly. Yuck.
I'd like to thank everyone that's emailed the kind messages about how much they like Sweet16 -- even when they have bugs to report as well. That's always nice when folks say, "Hey, even though I've got this problem to report, I'm sure happy you're doing this project." Beats getting chewed out, which I've had happen on other projects...