dim - Socoder

-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 0\|669\|0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Blitz -> dim
Mon, 10 Jan 2011, 20:03
dna	What is the Maximum value that NN can be in the statement dim(NN)? Also, when taking input for a dim, what is that max? I ask because I have my program hang when i input a number larger than 100000 -=-=- DNA
Mon, 10 Jan 2011, 21:27
dna	Just FYI. I used the Rand instead of the Rnd function and still after generating the data file I got a " " space embedded in the text. I then went to implicitly force the lower bound of 1, although the docs mention that its supposed to be done by the system, and thus far there are no " " spaces being generated by a random (pardon the pun) NULL or 0 (Zero). -=-=- DNA
Tue, 11 Jan 2011, 10:09
j\\'ordos	blitz gave a memory access violation error (with debug enabled) when I dimmed 1000000000, one zero less still worked fine.
Tue, 11 Jan 2011, 11:29
dna	Thanks for that information. My original post concerned the filling of the dimensioned array. When doing so in my program, there is a large pause. Also, you should know that I am using B2D. In B3D there might be a difference. -=-=- DNA
Tue, 11 Jan 2011, 11:36
j\\'ordos	When filling the array (with rand(2) ) I get the same limit. I can fill up to 1000000 of them instantly, though I suppose this depends mainly on your cpu & ram and even your hd? I'm using blitz3D though.
Tue, 11 Jan 2011, 14:21
dna	I have a Core 2 Duo with 1 Gig Ram, 30Gig drive w 21G free. It may be B2d then and if so then I might have to try a different method. -=-=- DNA
Tue, 11 Jan 2011, 14:53
JL235	Technically your graphics card should play a role as Windows needs to map some of your address space to video memory (so the bigger your card the less ram you have). But this only affects 32-bit systems. Otherwise your allowed to go up to around 3gb, regardless of your ram and CPU (thanks to virtual memory). Try using data banks, they might allow you to store more memory. It might be that BB's internal usage or arrays is more expensive then it needs to be and so is using tonnes of memory. However an array of 1000000 ints should only be using around 3.8mb, which is pitiful. Also AFAIK the language of Blitz2D and Blitz3D is identical (including it's implementation). It's only the libraries which differ (obviously the fact that BB3D has a 3D library).
Tue, 11 Jan 2011, 15:15
dna	That is interesting as well JL235. Something else may be going on here then. I also never knew that B3D was not that much different from B2D. I'm missing more fun. -=-=- DNA