Wanna Be A Commercial Real Estate Millionaire?
Imagine Yourself As A Commercial Real Estate Millionaire? 
Create 6- and 7-figure Incomes - With ZERO Risk!
Can you imagine yourself as a 
Commercial Real Estate Millionaire? 
We can! 
“Discover how people just like you now enjoy working from the comforts of home 
and creating 6- and 7-figure incomes - with zero risk - while our company does 
over 97% of all the work” 
Finally‚ you really can become financially independent and live the Life of 
Your Dreams… 
http://clickst.BOUNDLESS.hop.clickbank.net/


*
*
*
*
*
*
*
*
*
*
*
*
*
This is not spam. You receive this mail because you are a member of this yahoo 
group. If you do not wish to receive any more mails from this yahoo group, 
please follow these 3 steps:
- Scroll to the bottom of this page and find the links of Yahoo Groups at the 
very bottom of this page. 
- Click “Change setting via the web” link. You will be brought to the Edit 
Membership Page of this Yahoo Group.
- Change your message delivery (Step 2) option to “Web Only” instead of 
“Individual Email”
By selecting this option, you will be stil member of this yahoo group but will 
not receive individuacters and it could be possible that the above comparison
        // passes but one of the next one will fail and that is why we don't 
want
        // to update fCharIndex.  The other possibility is that it is called for
        // the matching endtag and the string could be really long, even longer
        // than the buffer which forces us to advance the fCharIndex position.
        if (srcLen < kCharBufSize/4) {            
            unsigned int saveCharsLeft = charsLeft;
            //fCharIndex += charsLeft;
    
            unsigned int offset = charsLeft;
            unsigned int remainingLen = srcLen - charsLeft;

            while (remainingLen > 0) {
                refreshCharBuffer();
                charsLeft = charsLeftInBuffer();
                if (charsLeft == 0)
                  return false; // error situation
                if (charsLeft > remainingLen)
                    charsLeft = remainingLen;
                if 
(XMLString::compareNString(&fCharBuf[fCharIndex+saveCharsLeft], toSkip+offset, 
charsLeft))
                    return false;
                offset += charsLeft;
                remainingLen -= charsLeft;
                saveCharsLeft += charsLeft;
            }
            fCharIndex += saveCharsLeft;

        }
        else {
            // a really long name            
            fCharIndex += charsLeft;
    
            unsigned int offset = charsLeft;
            unsigned int remainingLen = srcLen - charsLeft;

            while (remainingLen > 0) {
                refreshCharBuffer();
                charsLeft = charsLeftInBuffer();
                if (charsLeft == 0)
                  return false; // error situation
                if (charsLeft > remainingLen)
                    charsLeft = remainingLen;
                if (XMLString::compareNString(&fCharBuf[fCharIndex], 
toSkip+offset, charsLeft))
                    return false;
                offset += charsLeft;
                remainingLen -= charsLeft;
                fCharIndex += charsLeft;
            }            
        }
    }

    // Add the source length to the current column to get it back right
    fCurCol += srcLen;   

    return true;
}

I tested it with the program attached as well as the testcase with the really 
really long name and both work.  The kCharBufSize/4 was just a guess for a 
value.  Having a skippedEndString that advances the buffer might be cleaner.  I 
also noticed that the first line of this function is 
const unsigned int srcLen = XMLString::stringLen(toSkip);

Since the majority of the places calling this routine are passing in 
XMLUni::fgxxx strings we could pass in the length of the string to improve 
performance.

> Parser reports error when comment tag is broken up by BinInputStream
> --------------------------------------------------------------------
>
>                 Key: XERCESC-1827
>                 URL: https://issues.apache.org/jira/browse/XERCESC-1827
>             Project: Xerces-C++
>          Issue Type: Bug
>          Components: Non-Validating Parser
>    Affects Versions: 2.8.0
>         Environment: Solaris (SunOS 5.10) i386 SunPRO
> cygwin i386 GCC
>            Reporter: Vasantha Crabb
>             Fix For: 3.0.0, 2.9.0
>
>         Attachments: test.cc
>
>
> If the BinInputStream delivers data to the parser in such a way that the '<', 
> '!' and '--' at the start of an XML comment are delivered separately, the 
> parser will report the error 'Expected comment or CDATA'.  The problem is 
> reproducible under Xerces 2.8 on both Solaris i386 with the SunPRO C++ 
> compiler and cygwin i386 with the GNU C++ compiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to