Re: [listchars] request (was: Bug in capitalize ... ?)

This WebDNA talk-list message is from

2003


It keeps the original formatting.
numero = 53520
interpreted = N
texte = I look forward to the modifications :) On Tuesday, October 21, 2003, at 04:30 AM, Scott Anderson wrote: > 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/ > > Regards Stuart Tremain idfk web developments 114a/40 yeo street neutral bay 2089 australia t +612 9908 2134 f +612 9908 4837 ------------------------------------------------------------- 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:

    
  1. Re: [listchars] request (was: Bug in capitalize ... ?) ( Stuart Tremain 2003)
  2. Re: [listchars] request (was: Bug in capitalize ... ?) ( Kenneth Grome 2003)
  3. Re: [listchars] request (was: Bug in capitalize ... ?) ( Brian Fries 2003)
  4. Re: [listchars] request (was: Bug in capitalize ... ?) ( Scott Anderson 2003)
  5. [listchars] request (was: Bug in capitalize ... ?) ( Brian Fries 2003)
I look forward to the modifications :) On Tuesday, October 21, 2003, at 04:30 AM, Scott Anderson wrote: > 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/ > > Regards Stuart Tremain idfk web developments 114a/40 yeo street neutral bay 2089 australia t +612 9908 2134 f +612 9908 4837 ------------------------------------------------------------- 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/ Stuart Tremain

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:

[WebDNA] difference in formatting [time] (2011) Pithy questions on webcommerce & siteedit (1997) Adding more than one item and QTY to cart (2000) WebCat2final1 crashes (1997) RE: is sku a REQUIRED field on NT (1997) Re:Help name our technology! (1997) Protect (1997) Repost: Orderfile, Grandtotal: How do I get it to all add up. (2000) About WebDNA (2006) WebCatalog can't find database (1997) HTML Editors (1997) [WebDNA] My failed cPanel and WebDNA experience ... (2016) Grep Problems (2005) Search design (1997) Re:PCS Customer submissions ? (1997) emailer truncates last letter! (1997) Problems getting parameters passed into email. (1997) WebDNA Running Out of RAM? (2004) F3 crashing server (1997) Custom formulas.db (1998)