I was doing a search to find out what the code was for the quickstat | divider symbol (found it, it's #179) when I came across a script challenge. I was looking for the code so that I could write a script to get quickstat info for other scripts, and here it is, code that is much better and tighter than I could ever write with my paltry coding skills. Wanted to say excellent work from all of you coders in that challenge, you're all great coders.
Anyway, I copied it out and tried it, and it worked great. But then, gears in my amateur brain started turning, and I thought "What if I added a 2nd array, that would hold the types? Then, I could write the type and the number of each or what it is both to the file." So, my noob fingers started fumbling in the code, and I added a few lines I thought would work. Added a line to set my 2nd array, added a line to set an increment variable $i. Added a couple more lines and ran it. I got my array, but it didn't turn out like the array from +EP+ 's final code in the script challenge. So maybe you coders could take a look and tell me where I messed up. This is much more advanced coding than I can do, still not sure I understand a couple of the things that +EP+ 's code does. So I look forward to learning from this critique. The code follows. After that is a copy of the arrays from after I run the script.

EP's Excellent work


My Mangling of his beautiful work


Variables
Dynamic array of "$QUICKSTAT" (size 29)
"CORP" = "1"
"PHOT" = "0"
"SECT" = "4717"
"TYPE" = "IMPSTA"
"TURNS" = "0"
"CREDS" = "184462"
"FIGS" = "1469"
"SHLDS" = "1000"
"HLDS" = "150"
"ORE" = "150"
"ORG" = "0"
"EQU" = "0"
"COL" = "0"
"ARMD" = "50"
"LMPT" = "2"
"GTORP" = "2"
"TWARP" = "2"
"CLKS" = "2"
"BEACNS" = "2"
"ATMDT" = "2"
"CRBO" = "0"
"EPRB" = "5"
"MDIS" = "10"
"PSPRB" = "NO"
"PLSCN" = "NO"
"LRS" = "HOLO"
"ALN" = "1234"
"EXP" = "1305"
"SHIP" = "3"
"$QUICKSTATTYPE" = "0"

Dynamic array of "$QUICKSTATTYPE" (size 28)
"0" = "SECT"
"1" = "TURNS"
"2" = "CREDS"
"3" = "FIGS"
"4" = "SHLDS"
"5" = "HLDS"
"6" = "ORE"
"7" = "ORG"
"8" = "EQU"
"9" = "COL"
"10" = "PHOT"
"11" = "ARMD"
"12" = "LMPT"
"13" = "GTORP"
"14" = "TWARP"
"15" = "CLKS"
"16" = "BEACNS"
"17" = "ATMDT"
"18" = "CRBO"
"19" = "EPRB"
"20" = "MDIS"
"21" = "PSPRB"
"22" = "PLSCN"
"23" = "LRS"
"24" = "ALN"
"25" = "EXP"
"26" = "CORP"
"27" = "SHIP"
"$STAT" = "SHIP"

The 2nd set of array variables are from my array.

A similar method that can give you what you may be looking for, but not as tight as EP's example.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Hey Steve,
As you can see from the dynamic array that is created, the stat names are not created linearly as each value is parsed from the quickstat lines. You see that the CORP and PHOT array indexes are created first. This is done during the first pass of the code, in the second while loop test, on this line:
while ($block <> "") and ($quickStat[CORP] <> "INITIALIZE_TO_ZERO") and ($quickStat[PHOT] <> "@Zero")

Then, the SECT index is created, since it is actually the first value extracted from the quickstat line by getText here:
getText #179 & CURRENTLINE & #179 & #179 $block #179 #179

And then finally, the TYPE index is created, still in the first pass, by this line:
getWord $capsBlock $quickStat[TYPE] 3

Now, understand that the goal of the script challenge wasn't extensibility. That bit of code trades predictability (and legibility) for adaptability and brevity.

More to the point however, to iterate over the types and echo (or write to a file) their values, do this after my original quickstat routine has run:

Regards,
+EP+

Pro, thanks for that script example, works very well. I can even tell what you are doing with some of it, I will have to study it some more to figure out a few of the things you did there though

+EP+ thanks for the further explanation on your original code and the example code for how to set things up to echo or write the values, I am sure someday I will even figure out everything you are talking about - maybe after I take some programming classes? lol

Both of those posts were very informative, thanks for taking the time to give me (and others who read this) some useful instruction on these topics.

You are welcome and several parts of the script I posted are based on things EP has done and showed a lot of us. One major thing I learned about EP is that if you try something and put thought into it, then he seems to be more than willing to help. The bubble finder I wrote was a script I had banged my head against for a long time, and I found a code snippet EP had written and the light clicked for me.

[Edit] Also you will find that you are always tweaking code. The code I posted in its tightest form (for me anyway) is:



All data references would have to be to $qsText[XXXX] where XXXX is SECT, TURNS, ORE, or whatever it is that you want from the QS line. A var dump looks like:
Dynamic array of "$QSTEXT" (size 28)
"SECT" = "1641"
"TURNS" = "0"
"CREDS" = "39,701,433"
"FIGS" = "200,000"
"SHLDS" = "16,000"
"HLDS" = "255"
"ORE" = "255"
"ORG" = "0"
"EQU" = "0"
"COL" = "0"
"ARMD" = "0"
"LMPT" = "0"
"GTORP" = "13"
"TWARP" = "2"
"CLKS" = "0"
"BEACNS" = "0"
"ATMDT" = "19"
"CRBO" = "0"
"EPRB" = "0"
"MDIS" = "11"
"PSPRB" = "No"
"PLSCN" = "Yes"
"LRS" = "Holo"
"ALN" = "-479,107"
"EXP" = "32,809"
"CORP" = "3"
"SHIP" = "6"

If you checked your corp number with $qsText[CORP] and was not on a corp, it "should" return 0 even though the array was not created. It worked that way in the previous script because I did not have photons and the script did not crash. This did not answer your original question tho, but it shows yet another way of doing something.

[/Edit]

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Thanks Pro, some nice code there. I noticed a return there in the code in the last post, is that in there so that you can use it as an include and use the gosub command in another script that calls it?

And yes, I noticed what you were saying, you and +EP+ and many other scripters (I wish all the other scripters come to mind, I hate to leave out credit to others who are also helpful, although I am sure it would make my post much larger, there are so many of you that help) seem to be very helpful with noob scripter questions or questions on advanced stuff for scripters who might be running into a bit of a problem somewhere in their script - it's one of the things I enjoy about the forum.

I like the script challenges although they are usually above my level of scripting, what I am able to figure out from the posts are great learning experiences.

Yes, the return is for a gosub, but not necessarily just for an include. Gosubs are used in standalone (no includes) a lot to eliminate a lot of coding. Typically a quick stat would be an include since once written it usually doesn't require changes. Key word usually because some situations require the same basic code but with additions/changes.

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Beautiful, I couldn't have said it better myself. And I'm sure this goes for just about every scripter out there, that we don't want to write your scripts for you, but we're more than willing to nudge you in the right direction. Teach a man to fish, and all that.

Thanks for the props,
+EP+