--- In [email protected], "brucexs" <[EMAIL PROTECTED]> wrote: > > But: that batch of WCHARS will be full of x00s. Lots of unicode byte > > pairs include x00. > You have to return handles (which will iley just be pointers to > allocated memory) instead of actual strings and then write duplicates > for all the key string functions (lenght, search, replacechars, etc) > that work with the handles.
So I can't use ppsv->ReturnString(pszAllocTemp, szargs), presumably because it uses strcpy. Could you add ppsv->ReturnString(pszAllocTemp, szargs, count) or call it ppsv->ReturnBytes(pszAllocTemp, szargs, count) to the plugin interface? Maybe for security, just in case some idiot uses resulting "string" in a standard Powerpro function, you could bolt an extra '\0' on end, so standard string functions won't overrun? Would that work? Once a string is in your system, does your code rely on strcpy/strxxx a lot? How what happens when an argument is passed to plugin: strcpy happen? I can just tinker with large chunks of your clip and file plugin code, leaving only the basic string ops to code. > Its true that someone who wants unicode will have to do more work. Sure, gonna be a bit ugly. > This plugin is not that complicated but it will be tedious. Trying to minimise the tedium. Attention: PowerPro's Web site has moved: http://www.ppro.org Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/power-pro/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
