Re: [Adobe-source-devel] xstring questions

[Foster T. B. <fbr...@ad...>]

Yes, currently we're missing an API. One of the requirements for the  
string replacement code was to take the best possible source xstring  
based on the replacement tokens provided, which implied there was  
more than one source xstring -- currently all candidate strings are  
stored in a context, but this could be avoided in the case when you  
have one xstring and just want to flesh it out. I'll add it to the  
bugbase.

Blessings,
Foster


On Feb 11, 2006, at 02:04p, Sean Parent wrote:

> I suspect we're missing an API (I'd rather not have to go through a  
> context for replacement) - but I think you should be able to simply  
> create a local context as a workaround. I believe you also want to  
> be using the marker mechanism for the replacement (Foster?).

--
Foster T. Brereton              <}}}><              Romans 3:21-26
A d o b e   S o f t w a r e   T e c h n o l o g y   L a b
"What 99 percent of programmers need to know is not how to build  
components but how to use them." -- Alexander Stepanov