User Tim Nichols (email@example.com) posted:
Looks to me that you might need to use this in a WinSock or Tuxedo
environment when there is data to capture that has data outside the
printable character set range. In other words, if you are getting back
only ASCII data, there's no good reason to use this function instead of
lr_eval_string(). That is the first question you need to answer.
If you do end up using this function, you'll need to free the space
allocated by this function by calling lr_eval_string_ext_free().
If you look at the example (I have a 7.0 version of the product), can
you say which part of this function is not making sense? If you don't,
please paste the example you are looking at so I can talk in terms of
the code you see.