Re: [listchars] request (was: Bug in capitalize ... ?)
This WebDNA talk-list message is from 2003
It keeps the original formatting.
numero = 53492
interpreted = N
texte = Great suggestions. Along with a review of the [capitalize] code, we will add [listchars] and [searchstring] to the feature list for 5.2. -----Original Message----- From: Brian Fries [mailto:webdna@brainscansoftware.com] Sent: Monday, October 20, 2003 9:04 AM To: WebDNA Talk Subject: [listchars] request (was: Bug in capitalize ... ?) I second the request for [listchars]. I know you can mimic the behavior with current syntax, but a built-in [listchars] would be much more efficient. Current code: [loop start=1&end=[countchars][thetext][/countchars]] [text]char=[getchars start=[index]&end=[index]][/text] .... do what you need to with [char] [/loop] Improved code, with listchars added: [listchars [url][thetext][/url]] ....[char] and [index] context variables available to mess with [/listchars] Additionally, it would be great to include "start" and "end" parameters to [listchars] so you could process a range of characters. [listchars start=20&end=60&chars=[url][thetext][/url]] While I'm at it, I'd also love a [searchstring] tag that would tell me the offset of a specified substring within a given chunk of text: [text]offset=[searchstring string=[url][thetext][/url]&search=bobby&start=100][/text] would find the offset of the text "bobby" within [theText], starting at offset 100 (so you could then find the next occurrence). Would return zero if not found. I do a fair amount of large-block text processing, and these tools would make my code much more efficient. Thanks, Brian On Friday, October 17, 2003, at 06:36 PM, Kenneth Grome wrote: > A context like [listchars] might also be helpful in this situation as > a work-around. In fact I asked for [listchars] a couple years ago, > but the 'powers that be' at SMSI apparently did not value my > suggestion, so it's still not in the language -- and therefore we > still do not have a simple way of listing all the characters in a > particular string of text. > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Associated Messages, from the most recent to the oldest:
Great suggestions. Along with a review of the [capitalize] code, we will add [listchars] and [searchstring] to the feature list for 5.2. -----Original Message----- From: Brian Fries [mailto:webdna@brainscansoftware.com] Sent: Monday, October 20, 2003 9:04 AM To: WebDNA Talk Subject: [listchars] request (was: Bug in capitalize ... ?) I second the request for [listchars]. I know you can mimic the behavior with current syntax, but a built-in [listchars] would be much more efficient. Current code: [loop start=1&end=[countchars][thetext][/countchars]] [text]char=[getchars start=[index]&end=[index]][/text] .... do what you need to with [char] [/loop] Improved code, with listchars added: [listchars [url][thetext][/url]] ....[char] and [index] context variables available to mess with [/listchars] Additionally, it would be great to include "start" and "end" parameters to [listchars] so you could process a range of characters. [listchars start=20&end=60&chars=[url][thetext][/url]] While I'm at it, I'd also love a [searchstring] tag that would tell me the offset of a specified substring within a given chunk of text: [text]offset=[searchstring string=[url][thetext][/url]&search=bobby&start=100][/text] would find the offset of the text "bobby" within [theText], starting at offset 100 (so you could then find the next occurrence). Would return zero if not found. I do a fair amount of large-block text processing, and these tools would make my code much more efficient. Thanks, Brian On Friday, October 17, 2003, at 06:36 PM, Kenneth Grome wrote: > A context like [listchars] might also be helpful in this situation as > a work-around. In fact I asked for [listchars] a couple years ago, > but the 'powers that be' at SMSI apparently did not value my > suggestion, so it's still not in the language -- and therefore we > still do not have a simple way of listing all the characters in a > particular string of text. > -- Brian Fries, BrainScan Software -- http://www.brainscansoftware.com -- ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/ ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://webdna.smithmicro.com/
Scott Anderson
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
Re1000001: Setting up shop (1997)
Autonumber in Table (2006)
WebCatalog [FoundItems] Problem - AGAIN - (1997)
Inventory Adjustment (2000)
RE: Formulas.db + Users.db (1997)
Return records from another (1997)
WebCat2.0 [format thousands .0f] no go (1997)
[WebDNA] Passing a text variable via copyfile (2019)
Ampersand (1997)
What the *(**&^* webcat/mer (1998)
[WebDNA] New Webdna framework ! ... (addresses some initial concerns... coming into the design of a large project) (2012)
Dual 2GHz G5 (2003)
Mozilla/4. and Browser Info.txt (1997)
OT: Portland Oregon (2002)
WebCat2 - [format thousands] (1997)
Have I lost my mind? uhmm... (2002)
2.0Beta Command Ref (can't find this instruction) (1997)
Delete Context - to remove record (1998)
For those of you not on the WebCatalog Beta... (1997)
no global [username] or [password] displayed ... (1997)