On 2006-02-18, at 10:13 , Gregg Lebovitz wrote:
christian,If you found a function that does what you need then of course use that. I spent some time looking at the various string classes and it looks to me like byte_string and unistring are part of the old String class. I think byte_string and unistring are currently '#defined' as String. The new replacement are OUstring and Ustring in the rtl libraries.Gregg [EMAIL PROTECTED] wrote:To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=15666 ------- Additional comments from [EMAIL PROTECTED] Sat Feb 18 05:17:24 -0800 2006 ------- Gregg,I looked at all the code and I think I can take the search method from the String class and write a function that will take an array of chars and search simultaneously for all of them.Sorry, I must have missed something. As I mentioned, I already found SearchChar() which does exactly this. Shouldn't I use this method of the warning in string.hxx: "THIS CODE IS DEPRECATED. DO NOT USE IT IN ANY NEW CODE. Use the string classes in rtl/ ustring.hxx and rtl/ustrbuf.hxx (and rtl/string.hxx and rtl/ strbuf.hxx for byte-sized strings) instead." I just discovered this while looking around because of your comment. So if this SearchChar() method should be reimplemented in the String class, you can of course do this. I don't get the difference between ByteString/UniString and String at the moment (besides that String looks like it misses many functions and isn't Unicode-capable). Christian --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/ project_issues.html#notification-- Gregg Lebovitz [EMAIL PROTECTED] 617 233-5504 Fax: 309 408-1476--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Greetings,You have responded to an automatically generated message from the Issue Tracker. You cannot respond directly to these messages. Please log onto the website, go to the issue, and enter your comments in the Additional Comments box. When you are finished with your edits to the issue, click the submit button to update the issue report with your comments. This is how we keep all notes related to issues organized and available to all in the community.
To see the Additional Comments box on the issue report, you must be logged in, and your cookies must be enabled. Type in your user name and password into fields displayed in the upper right corner, then click the Login button. If you do this from the Home page, you may have to click Login again on the Login Page. When you are logged in, it will show that you are Logged In, and there will be a button displayed in the upper right corner for you to click when you are ready to log out.
Once you are logged in, you will be presented with a page called My Start Page under the My Pages tab, and the left menu will show links to tools. You can jump directly to your issue, by typing a number in the input box in the right column of My Start Page, or you can select My Issues from the Tools menu to see a list of your issues with an open status. You can show a list of *all* your issues by choosing 'Edit Query' and selecting additional choices in the Status field, by clicking on them with your Control key pressed down, then click on 'Submit Query'.
To send attachments regarding issues, please attach the file directly to the issue. Use the link "Create a new attachment" on the issue and then select Binary file (application/octet-stream) where asked, "What kind of file is this?" if your file's type does not show in the list.
Thanks, The OpenOffice.org Team
smime.p7s
Description: S/MIME cryptographic signature
