realbasic-nug
[Top] [All Lists]

Re: Quickest way to build a string?

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Quickest way to build a string?
From: Jeremy Cowgar <jeremy@cowgar.com>
Date: Thu, 29 Jan 2009 18:39:51 -0500
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <E51786AC-94C3-411B-B0FC-1E74A0D453CA@stretchedout.com>
References: <498238EF.4010801@cowgar.com> <E51786AC-94C3-411B-B0FC-1E74A0D453CA@stretchedout.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com
User-agent: Thunderbird 2.0.0.19 (Windows/20081209)
Greg O'Lone wrote:
Jeremy,

What are you trying to accomplish? There are a number of approaches (including some that use memoryblocks for speed), but if you just want to deal with a string, why not:

myString = "John Doe had a dog. "

or are you expecting the data to come into your program in pieces?

Right now I am parsing wiki text converting it into RTF. I may have something like:

----------------------
= Heading 1

This is a paragraph and **this is bold**, but //this is italic//.
----------------------

So, I am parsing it, when I get a chunk parsed (say "= Heading 1" should be "{\fs24 Heading 1}\par "), then I am appending the appropriate "RTF Prefix", the text and the appropriate "RTF Suffix" to a string, that in the end will be a string suitable for saving as a RTF file.

Jeremy


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>