Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Compiler Error C3049 "String Space Exhausted" 1
- Thread starter socalwiz
- Start date
Maybe you are running out of conventional memory (that one below 640Kb) and you are declaring inline arrays that are too large.
This problem can be resolved by reducing the size and/or
number of strings and arrays that are active at any one time. Probably the most common cause of this error is the declaration of extremely large arrays (e.g., LOCAL aArray[500][300]). Note that every array element requires memory to store -- even if its value is NIL -- and that the number of array elements in an array is determined by multiplying the number of elements in every dimension and adding the sum of all dimensions except for the last. For example, a 500x300 array has (500x300) + 500, or 150,500, elements.
Because every array element in Clipper requires 14 bytes, this amounts to 150,500 x 14, or 2,107,000 bytes -- well in excess of one megabyte and therefore potentially dangerous.
Note: There is no benefit gained by reusing arrays. Clipper is much more efficient when strings and arrays are thrown away and rebuilt often rather than kept around unnecessarily for long durations.
If this doesn´t help you, please post a new message indicating the memory map of your machine (remember the dos command MEM) and comment more about the prg where the problem bombs.
This problem can be resolved by reducing the size and/or
number of strings and arrays that are active at any one time. Probably the most common cause of this error is the declaration of extremely large arrays (e.g., LOCAL aArray[500][300]). Note that every array element requires memory to store -- even if its value is NIL -- and that the number of array elements in an array is determined by multiplying the number of elements in every dimension and adding the sum of all dimensions except for the last. For example, a 500x300 array has (500x300) + 500, or 150,500, elements.
Because every array element in Clipper requires 14 bytes, this amounts to 150,500 x 14, or 2,107,000 bytes -- well in excess of one megabyte and therefore potentially dangerous.
Note: There is no benefit gained by reusing arrays. Clipper is much more efficient when strings and arrays are thrown away and rebuilt often rather than kept around unnecessarily for long durations.
If this doesn´t help you, please post a new message indicating the memory map of your machine (remember the dos command MEM) and comment more about the prg where the problem bombs.
- Thread starter
- #3
I'm only getting this when I the one prg tries to compile. The rest of the 15 plus program compile just fine. Did not have this happen before. I am not the one who wrote this program, I only make minor changes in support of it. At the point I compile it, I have 603 mb of conventional ram. If you can think of anything that can aid in this, it would be greatly appreciated. Thank you
-
1
- #4
- Status
Similar threads
- Locked
- Question
- Locked
- Question