Multiple Dimensional Array v's Type Statement

[Dimster]

I found I just like the looks of Select Case over If.. statements and where possible I prefer to nest an IF statement in a Select Case .. just for the look of it. Now I'm writing a larger program with a lot more saving and retrieving from files. Again, just because I liked the look of it I have been using Type Statements rather than multi dimensional arrays. It's not too late for me to rethink, and recode for better efficiency - as my program gets larger and data handling increases, is there any particular advantage the array would have over the Type?

[bplus]

I'd say the main advantage (and maybe the only) of Type is making your code readable and understandable 3 years from now.

You also have a 3rd option, maybe considered the most primitive but still very readable and that is to have a separate single dimension array for what would be each line in the Type definition and a common index would keep all the values in sync.

A multi-dimensional array would be my last choice but it is a matter of preference.

Append: TYPE has more advantages, excellent for fixed record size for data basing and with Type you can have an array of mixed typed variables. With a multi-dimensional array, you are stuck with one type.

[Dimster]

Thanks. and Merry Christmas, Happy New Year, Happy Birthday, Happy Halloween and all those other happy events I have missed. I hadn't considered going to much smaller uni-arrays, so to speak. Back to the drawing board.

[bplus]

I appended two more advantages with a Type Array. Season's Greetings back to you!

[OldMoses]

I have to agree with Bplus on the readability of the TYPE over a multidimensional array. I feel like I have half a chance of figuring out what I was doing later on. Even so, with a good comment section to lay out the scheme, it wouldn't be too hard to get up to speed again.

[Dimster]

I appreciate that Andy. TYPE without the comments does give a better "look" to the logical flow, and with the comment section hopefully you can pass your code onto the grand kids and they may have some chance to understand where you were going with it all. I'm just now working on breaking up an old TYPE statement into the various individual, singular arrays. Lot more 'commenting' seems to be needed as I'm losing track of which array connects with which other array - had to rename them with a common theme.

[FellippeHeitor]

An array of a custom type is much more readable and kind of resemble modern languages' classes.

In the end all options are indeed valid code and it boils down to personal preference.

[xra7en]

I'd say the main advantage (and maybe the only) of Type is making your code readable and understandable 3 years from now.

You also have a 3rd option, maybe considered the most primitive but still very readable and that is to have a separate single dimension array for what would be each line in the Type definition and a common index would keep all the values in sync.

A multi-dimensional array would be my last choice but it is a matter of preference.

Append: TYPE has more advantages, excellent for fixed record size for data basing and with Type you can have an array of mixed typed variables. With a multi-dimensional array, you are stuck with one type.

another advantage - is if your a text gamer (like me hehehe), makes game saves a breeze! Just stuff player with all vars relating to player and then if needed, all dynamic game vars in a UTD, and then save both to a file..

[Dimster]

xra7en - That's interesting. I haven't really worked with UTD, as most of my arrays are working with values. Doesn't UTD work mostly with strings? Have to confess I did come across UTD a while ago and came away with thinking it mostly stores and retrieves words. I guess a value can be STR$'d

[bplus]

UTD?

I've heard of UDT (User Defined Type) but not UTD??

Probably mean UDT given subject  of this thread.  ;-))

[SMcNeill]

UTD?

I've heard of UDT (User Defined Type) but not UTD??

Probably mean UDT given subject  of this thread.  ;-))

I’ve worked with some databases that used UDT as an abbreviation for User Data Type, which is what I assumed it was representing here; though you’re probably correct in assuming it was originally just a typo.

[Dimster]

My apologizes, my mind went to Universal Text Data.

[xra7en]

UTD?

I've heard of UDT (User Defined Type) but not UTD??

Probably mean UDT given subject  of this thread.  ;-))

I’ve worked with some databases that used UDT as an abbreviation for User Data Type, which is what I assumed it was representing here; though you’re probably correct in assuming it was originally just a typo.

dyslexia...
but I mean what you know...

[xra7en]

its kdnda lkie redaing tihs mesasge. If you go wtih the folw, you knida get the gist of waht I was tyring to say LOL

(old  trick on how peoples minds can be when reading. we just fill in the gaps)

[bplus]

its kdnda lkie redaing tihs mesasge. If you go wtih the folw, you knida get the gist of waht I was tyring to say LOL

(old  trick on how peoples minds can be when reading. we just fill in the gaps)

Code: QB64: [Select]

1. _TITLE "Scampling" 'B+ translated from JB to QB64 only changingmsg$() and adding this line,  2019-12-26
2. 'scampling.txt for JB v1.01 [B+=MGA] 2016-05-15
3. 'modified for JB from scampling.bas SmallBASIC 2015-09-02 MGA/B+
4.  
5. '2018-12-27 need Randomize
6. RANDOMIZE TIMER
7. '2018-12-27 oops missed RND(0)
8. PRINT RND(0) ' always returns the last value returned
9.  
10.  
11. DIM msg$(3)
12. 'see if scample$ can unscramble some of following by accident
13. msg$(1) = "its kdnda lkie redaing tihs mesasge. If you go wtih the folw, you knida get the gist of waht I was tyring to say LOL"
14. msg$(2) = "(old  trick on how peoples minds can be when reading. we just fill in the gaps) "
15. msg$(3) = "THIS MESSAGE SHOWS YOU, THAT THE CAPABILITIES OF YOUR BRAIN ARE REALLY GREAT!"
16.  
17. punc$ = " <,>.?/:;'{[}]|\!@#$%^&*()_-+=" + CHR$(34)
18.  
19. FOR m = 0 TO UBOUND(msg$)
20.     lastp = 0: build$ = ""
21.     FOR i = 1 TO LEN(msg$(m))
22.         IF INSTR(punc$, MID$(msg$(m), i, 1)) THEN
23.             wrd$ = MID$(msg$(m), lastp + 1, i - lastp - 1)
24.             build$ = build$ + scample$(wrd$) + MID$(msg$(m), i, 1)
25.             lastp = i
26.         END IF
27.     NEXT
28.     IF lastp < LEN(msg$(m)) THEN
29.         wrd$ = MID$(msg$(m), lastp + 1)
30.         build$ = build$ + scample$(wrd$)
31.     END IF
32.     PRINT build$
33. NEXT
34.  
35. FUNCTION scample$ (wrd$)
36.     IF wrd$ = "scramble" THEN scample$ = CHR$(34) + "scample" + CHR$(34): EXIT FUNCTION
37.     IF wrd$ = "a" THEN scample$ = "aa": EXIT FUNCTION
38.     IF LEN(wrd$) THEN
39.         flaglower = 0
40.         FOR i = 1 TO LEN(wrd$)
41.             IF INSTR("abcdefghijklmnopqrstuvwxyz", MID$(wrd$, i, 1)) THEN flaglower = 1: EXIT FOR
42.         NEXT
43.         IF flaglower THEN 'just mess up the word a little, leave first and last letter the same
44.             IF LEN(wrd$) > 3 THEN
45.                 lp = INT(RND * (LEN(wrd$) - 3)) + 2
46.                 wrd$ = MID$(wrd$, 1, lp - 1) + MID$(wrd$, lp + 1, 1) + MID$(wrd$, lp, 1) + MID$(wrd$, lp + 2)
47.             END IF
48.         ELSE 'all upper case letters so do a different substition numbers for letters and vice versa
49.             bld$ = ""
50.             FOR ch = 1 TO LEN(wrd$)
51.                 L$ = MID$(wrd$, ch, 1)
52.                 SELECT CASE L$
53.                     CASE "A": s$ = "4"
54.                     CASE "4": s$ = "A"
55.                     CASE "B": s$ = "8"
56.                     CASE "8": s$ = "B"
57.                     CASE "E": s$ = "3"
58.                     CASE "3": s$ = "E"
59.                     CASE "G": s$ = "6"
60.                     CASE "6": s$ = "G"
61.                     CASE "I": s$ = "1"
62.                     CASE "1": s$ = "I"
63.                     CASE "O": s$ = "0"
64.                     CASE "0": s$ = "O"
65.                     CASE "S": s$ = "5"
66.                     CASE "5": s$ = "S"
67.                     CASE ELSE: s$ = L$
68.                 END SELECT
69.                 bld$ = bld$ + s$
70.             NEXT
71.             wrd$ = bld$
72.         END IF
73.     END IF
74.     scample$ = wrd$
75. END FUNCTION
76.  
77.  

EDIT: Oops, I forgot JB handles RND differently than QB64, code has been updated.