Skip to content
Prev 14437 / 63424 Next

Problem with read.xport() from foreigh package (PR#7389)

On Tue, 23 Nov 2004 ruskin@iba.com.hk wrote:

            
There is no Windows-specific version of read.xport(), so that change 
happened everywhere: but that message does not say it was fixed nor which 
change might have fixed it.  I am guessing the change is this one

2002-03-27  Douglas Bates  <bates@stat.wisc.edu>

         * src/SASxport.c (IS_SASNA_CHAR): Silly typo (0x4l, not 0x41)
         caught by Peter.

and that does not sound like the same thing.
^^^^^^^^^^^^^^^^^^^^

What does that mean?  It `works' on its test suite: none of the changes 
since 0.8 are related to this question.  I don't believe there is an 
example in the test suite with one-char strings, and we need an example to 
reproduce what you are seeing.

So, please read the posting guide and provide us with a reproducible 
example.