Problem with StringRegExp

[Worfox]

hei

I have a string :

$str = "11BlahBlahbla123bla{CODE"1337"}blabla{{{}}}{}blaaa{CODE"7331"}bla..."

and i want to convert this string to a array

so it look like this:

$anarray[0] = 11BlahBlahbla123bla
$anarray[1] = 1337
$anarray[2] = blabla{{{}}}{}blaaa
$anarray[3] = 7331
$anarray[4] = bla...

i found the best effect with

StringRegExp(StringRegExpReplace(StringRegExpReplace($str, '{CODE', ''), '}', ''), '[\w\.]+', 3)

but it does not work well

[Nahuel]

I don't think I get it... what's the pattern to follow? What do you want to use as a delimiter to know where to split the string? I tested the code you posted and it seems to do what you want... what does "but it does not work well" really mean?

[MrCreatoR]

Like this:

#include <Array.au3>

$Str = '11BlahBlahbla123bla{CODE"1337"}blabla{{{}}}{}blaaa{CODE"7331"}bla...'

$aArray = StringRegExp($Str, '\A(?i)(.*)\{CODE"(.*)"\}(.*)\{CODE"(.*)"\}(.*)', 3)
_ArrayDisplay($aArray)

?

[trancexx]

@MrCreatoR; I think that '...' in his string means that there could be more rather then just '...'

Possible solution:

StringRegExp(StringRegExpReplace($e, '{CODE"(\d{4})"}', ' $1 '), '\S* ', 3)

[Worfox]

Like this:

#include <Array.au3>

$Str = '11BlahBlahbla123bla{CODE"1337"}blabla{{{}}}{}blaaa{CODE"7331"}bla...'

$aArray = StringRegExp($Str, '\A(?i)(.*)\{CODE"(.*)"\}(.*)\{CODE"(.*)"\}(.*)', 3)
_ArrayDisplay($aArray)

?

>_<

Hei thank you MrCreatoR this one works perfect

[Worfox]

Edit:

uuh sorry, tha max of the code things are 2, but there could be unlimited of theese code things...

To Explain my problem here a example:

the string = 'TextTextTextorsomething{CODE"Number1"}{CODE"Number2"}textblahorwhatever{CODE"Number3"}texttextandeverything' and so on...

the array

[0] = TextTextTextorsomething

[1] = Number1

[2] = Number2

[3] = textblahorwhatever

[4] = Number3

[5] = texttextandeverything

i need the numbers to activate some functions in my script, and i need the text before and after the codenumberthing.

If $ar[$i] = *anumberfrom 1 to n* then
 controldosomething
else
 controldosomethingwiththetext
endif

[MrCreatoR]

i need the text before and after the codenumberthing

Ok, i can't find a way to do it using StringRegExp(), so here is another method, using loop on StringSplit()...

#include <Array.au3>

$String = 'TextTextTextorsomething{CODE"Number1"}{CODE"Number2"}textblahorwhatever{CODE"Number3"}texttextandeverything'

$aArray = _GetCodesArray($String)
_ArrayDisplay($aArray)

Func _GetCodesArray($sString)
    Local $aSplit = StringSplit($String, '{CODE"'), $aResArray[1]

    For $i = 1 To UBound($aSplit)-1
        If $aSplit[$i] <> '' And $aSplit[$i] <> '}' Then
            If StringLeft($aSplit[$i], 1) = "}" Then $aSplit[$i] = StringTrimLeft($aSplit[$i], 1)
            
            $aResArray[0] += 1
            ReDim $aResArray[$aResArray[0]+1]
            $aResArray[$aResArray[0]] = $aSplit[$i]
        EndIf
    Next
    
    Return $aResArray
EndFunc

[trancexx]

#include <Array.au3>

$Str = 'TextTextTextorsomething{CODE"3456"}{CODE"4567"}textblahorwhatever{CODE"3234888"}texttextandeverything{CODE"3299"}dfghjhfgjh}{hh'

$array = StringRegExp(StringRegExpReplace($Str, '{CODE"(\d*)"}', '§$1§') & '§', '(?s)(.*?)§+', 3)
_ArrayDisplay($array)

[Worfox]

trancexx, i think you got it

i cant use the § sign, but thats no problem...§ is rarely used

Edited September 12, 2008 by Worfox

[Community On Patrol]

Hi Worfox,

1st Welcome to the AutoIt Forums!

Some of the following tips may not apply to you, but it may make your life a bit easier here on the forum in the future.

CODE

• Did you know that we have an awesome search feature?

  You can find many answers to your current questions, just by typing in the right search patterns.

• A suggestion is to use the Advanced Search mode:

• Type your specific search term in quotes.
• Click the forum you want to search in (the one most likely to have your information would generally be the Example Script forum and or the General Help and Support Forum).
• Click on "Search titles only" radio button.
• Click perform search.

The above will help you narrow down your searches and prevent you from unneccesarily posting a new thread.

[*]Also, you should try to read the Sticky posts that are at the top of each of the AutoIt Forums you enter such as:

• FAQs (Frequently Asked Questions)

• Are my AutoIt EXEs really infected? (About false positives and what to do if you may encounter one)

[*]Forum Etiquette:

• Making a new thread:
  • Use the Search feature first to see if your question has already been answered.
  • Look in the help file as well before even thinking of posting (When what you want could be obtained by simply reading the help file, you don't generally get a good response from your AutoIt community).
  • Titles are very important here. 1 word titles or titles like "help me", "write something for me", "I'm a noob" etc... aren't tolerated.
  • Use common sense when creating a new thread.

    Ask yourself if the title is descriptive enough to even interest someone (preferably those that know what they are talking about) to even look at your thread, let alone reply in it.

  • Think about how it would show in the search feature if someone were to look for something just like you are looking for (think of the keywords you used yourself and obviously didn't find anything (because we know you used the search feature ) and use those types of keywords in your title as well).
• Thread content:
  • Be descriptive with your query. (Make sure we actually know what you want to do).
  • Show you've made an effort in coding what you want (provide the reproducer code (generally no more than 50 lines as people lose interest in debugging someones script for free)).
  • Don't talk in ebonics. A lot of the forum members are adults, and a lot of them know how to help you, but talk like a child, you'll be treated as such.
  • Don't ask for help making keyloggers, spam (even if it's to do as a prank), or anything that can be thought of as malicious. You'll more than likely have the thread locked by a moderator, and take a bashing from your fellow AutoIt community.
  • When posting code, use code boxes. This can be accomplished by using [code ]<content here>[/code ] (No spaces between the brackets []).

    Using code boxes will keep the indentation and make it easier to read for others to help you.

• Bumping your threads:
  • Use common courtesy here.

    Keep in mind every time you bump your thread to the top of the forum, you knock the other threads down a notch.

    Everyone posting for help has just as much right for their threads to get read as you do.

    Because of that, do not bump your post more than once in a 24 hour period.

    A Bump is simply posting in your thread with nothing that pertains to your query with the sole purpose of moving it up.

    Deleting previous bumps, and posting new ones is not tolerated, and the moderators can find those deletions, so do yourself a favor and don't cross that line >_< .

• Rude or obnoxious content:

  This falls pretty much under the common sense thing. If you use it (common sense) before posting, you won't have issues.

  • Don't use foul language, remember, a lot of the community is at work when they read these threads.
  • Don't provoke or instigate an argument with someone.
• Double Posting:
  • It's understood that sometimes there's a lag in the system, and sometimes people don't see their post go up right aways so they post again.

    If this happens to you, simply notify a moderator with the report feature in the post, and politely ask them to delete it.

  • If you're just creating another topic because your original topic is not being answered the way you want or at all, this is not tolerated. You could lose your posting privileges all together over it.
• Non-English languages
  • If English is not your primary language, please make an attempt to interpret (yourself or online) and post that interpretation.

    We have wonderful users from around the world, so after you've done your post in English, back it up with your question also in your native tongue (You may find your answer much quicker using both).

That's it for now, I hope you have a wonderful learning experience, and hope to see you contribute to the community as your knowledge grows.

[Worfox]

Yeah ty,

i double posted because i could not edit my post, so i created a new...

Sorry if i made some grammar mistakes, im german and its a school english^^

and it looks pretty nice here