DIM SHARED, COMMON SHARED

[oracle]

I'd use DIM SHARED where possible. COMMON SHARED (AFAIK) will use more memory if many modules are used than DIM SHARED. And COMMON SHARED arrays... I think you have to DIM the array then COMMON SHARED it, which is just silly

[Agamemnus]

I don't just use people's source code, I steal it and then change it so that no one knows I stole it.

[SCM]

It's true. After Aga is done with it no one would recognise it.

[webberboy]

Im self taught too, but I also use snitbits of others codes, sometimes modified, sometimes not... For example, the challenge I won at http://forum.qbasicnews.com/viewtopic.php?t=4963 was won buy taking someone elses 3d code and adding some other elements to it to make it red/blue, ect.

[elspork]

Great. Thanks.

I suppose it would be better still to avoid the universal variables whenever possible. I'm still working on that. I make liberal use of subroutines, and sometimes it gets complicated for simple me to selectively import variables that get used frequently.

confession: I have actually been using exclusively universal variables. I haven't had any memory problems yet (that I know of), but perhaps my programs would speed up like when I converted to DEFINT A-Z.

Well, actually I HAVE had memory problems. I've been assuming they were due to problems running QB in Microsquish.

[elspork]

Regarding self-teaching:

I think that is part of the draw to QBasic. There is such an element of discovery for someone like me, who is only a hobbyist programmer. I'm actually a sculptor and designer, but programming is the best creative problem solving medium I've found. Learning Qbasic in particular at this point is more a matter of community sharing than education. It is a lot more exciting to dismantle somebody else's code to learn than to read a book.

I started in Qbasic about twelve years ago with my best friend. It was just the two of us in his basement, with the qb help file. We were thrilled when we figured out the PALETTE function. We could manipulate colors! it was two years before we figured out it did more than black to bright red, but we were thrilled nonetheless. Now, I get on the internet, and there are thousands of programs much better than my own to dismantle and figure out.

[TheBigBasicQ]

I'd use DIM SHARED where possible. COMMON SHARED (AFAIK) will use more memory if many modules are used than DIM SHARED. And COMMON SHARED arrays... I think you have to DIM the array then COMMON SHARED it, which is just silly

Oracle, are you *sure* you know COMMON SHARED and used it properly?

Because when using arrays you need to do something like this:

Module 1:
COMMON SHARED my_arr()
DIM SHARED my_arr(10) AS INTEGER

my_arr(1) = 14
blah blah blah...

Module 2:
COMMON SHARED my_arr1()


DIM SHARED my_arr1(10) AS INTEGER

print my_arr1(1)
blah blah blah...

Output:
14

The order of declaration matters and not the name of the variable. Also, you need to COMMON SHARED it before you DIM it .

I dunno what memory problems you had but I am using COMMON SHARED in my GUI which has 5 modules and it works fine without any memory problem and it compiles from within the QB-IDE.

[TheBigBasicQ]

Regarding self-teaching:

I think that is part of the draw to QBasic. There is such an element of discovery for someone like me, who is only a hobbyist programmer. I'm actually a sculptor and designer, but programming is the best creative problem solving medium I've found. Learning Qbasic in particular at this point is more a matter of community sharing than education. It is a lot more exciting to dismantle somebody else's code to learn than to read a book.

I started in Qbasic about twelve years ago with my best friend. It was just the two of us in his basement, with the qb help file. We were thrilled when we figured out the PALETTE function. We could manipulate colors! it was two years before we figured out it did more than black to bright red, but we were thrilled nonetheless. Now, I get on the internet, and there are thousands of programs much better than my own to dismantle and figure out.

Wow, the story of my friend and me is almost exactly same =P. I too used the QB help file until 4 years ago when I got my first internet connection. I still depend only on the help files. And occassionally I give these guys questions to ponder upon :lol:

[relsoft]

It's true. After Aga is done with it no one would recognise it.

LOL

Aga: If you make that iterative Qsort routine of yours readable, I might have some use for it. :*)

[Neo]

I dunno what memory problems you had but I am using COMMON SHARED in my GUI which has 5 modules and it works fine without any memory problem and it compiles from within the QB-IDE.

Did you try commoning DIM SHARED Level(16, 2000) AS INTEGER? We tried but we got out of memory each time. Making a remark of the COMMON SHARED line solved the prob, but I did more than that because I think declaring arrays in includes is a bad idea