ExternalArray of Strings

> Günther,
>
>> how do I assemble an ExternalArray of Strings to pass it to a C function?
>
>
> Most C functions that I have seen do this via one string of characters
> with single nulls to terminate/separate the strings, and two nulls in a
> row to mark the end of the array.
>
> The following (untested!!) should do more or less what I described:
>
> | out |
> out := ByteArray writeStream.
> someStrings do:[ :each |
>    out nextPutAll:each asByteArray; nextPut:0.
> ].
> out nextPut:0.
>
> It is also possible to pass an array of addresses of individual buffers.
>  It all depends on what the function expects.
>
> Have a good one,
>
> Bill
>

> This is a description of the function:
>
> Function: xsltApplyStylesheet
>
> xmlDocPtr    xsltApplyStylesheet    (xsltStylesheetPtr style,
>                      xmlDocPtr doc,
>                      const char ** params)
>
> Apply the stylesheet to the document NOTE: This may lead to a
> non-wellformed output XML wise !
> style:    a parsed XSLT stylesheet
> doc:    a parsed XML document
> params:    a NULL terminated arry of parameters names/values tuples
> Returns:    the result document or NULL in case of error
>
> where "> const char ** params)"
>
> is the unresolved part

>> xmlDocPtr    xsltApplyStylesheet    (xsltStylesheetPtr style,
>>                      xmlDocPtr doc,
>>                      const char ** params)
> It sounds like an array of pointers to the "strings" with a null in the
> last slot so they can tell when to quit.  One way to do that would be to
> build a DWORD aray by sending #yourAddress to each of the string/value
> tuples.  That assumes that a tuple is a String, which it almost has to
> be given their definition.  You will need to uncover their syntax; it is
> probably either name=value, something more natural to XML, % encoding,
> etc.  Do you have any examples?

> Bill Schwab wrote:
>
>>> xmlDocPtr    xsltApplyStylesheet    (xsltStylesheetPtr style,
>>>                      xmlDocPtr doc,
>>>                      const char ** params)
>>
>> It sounds like an array of pointers to the "strings" with a null in
>> the last slot so they can tell when to quit.  One way to do that would
>> be to build a DWORD aray by sending #yourAddress to each of the
>> string/value tuples.  That assumes that a tuple is a String, which it
>> almost has to be given their definition.  You will need to uncover
>> their syntax; it is probably either name=value, something more natural
>> to XML, % encoding, etc.  Do you have any examples?
>
>
> Günther,
>
> are you wrapping the library manually? If my assumption is correct the
> XSLT library contains a "few more" functions, structures and constants.
> You might consider transforming the header files in IDL and then let the
> AXTypeLibraryAnalyzer do the hard work for you ...
>
> CU,
>
> Udo