[Implemented] Multi dimensional array support in structures!
Not Quite So...
Properly supported, fixed length strings are assigned and used just as VL (variable Length) strings are. Instead of peeking and poking, you use them in assignments with the (=) operator, or you can use LSET() or RSET() commands, which cause them to be assigned with padding characters of either zeros or spaces (there is a setting to control which). The LSET() causes them to be left-justified in the allowed string space, and RSET() allows them to be right-justified in the allowed string space. If a fixed string corresponds to a column, this makes it easy to determine if the string contents are to be sorted based on anlphanumeric order (left justified), or primarily on quantity or length (right justified), such as a column of numerical values. One language also added an MSET() command to allow you to pad a string to sit in the middle of a string space, useful perhaps for defining a column the with of a sheet of paper and centering a header or title in that area. Of course the MSET() uses spaces when padding on the left side, and the padding on the right side can be either nulls or spaces (same controlled setting for LSET() and RSET().
The same support for strings recognizes ASCIIZ (null, or zero-terminated ASCII strings) as found in PB and C/C++, and when assigning a ASCIIZ to a fixed length string or vice versa, the assignment automatically makes the necessary adjustments - if from an ASCIIZ to a fized length string, the copy ends if the end of the fixed string is reached first, or if the zero (null) byte is reached, the copy continues, filling in the zero or space padding characters for the balance of the fixed string space. The assumption with fixed length strings is that they are left-justified in the string space unless RSET() or MSET() is indicated, as this is the more common expression method.
The same support for strings recognizes ASCIIZ (null, or zero-terminated ASCII strings) as found in PB and C/C++, and when assigning a ASCIIZ to a fixed length string or vice versa, the assignment automatically makes the necessary adjustments - if from an ASCIIZ to a fized length string, the copy ends if the end of the fixed string is reached first, or if the zero (null) byte is reached, the copy continues, filling in the zero or space padding characters for the balance of the fixed string space. The assumption with fixed length strings is that they are left-justified in the string space unless RSET() or MSET() is indicated, as this is the more common expression method.
has-been wanna-be (You may not agree with what I say, but it will make you think).
Shannara, your tone is getting down right ugly in these forums of late!You guys, this have NOTHING to do with this thread, take this elsewhere please.

No need to apologise Dare2.Apologies, Shannara.
Kale, I think we all somwhow feel that a great product like PureBasic belongs to us all, and we can sometimes get impatient when we run up against a limitation what prevents us from doing something that we feel should be within its scope. None of us like to concede ground to other development systems, and we all feel that it should only be a matter of time until those limits are addresses.
You have been right on concerning the unmistakable rudeness that a few choice individuals have shown, and trying to make the point that I haven't written a game so I'm hardly qualified to speak on some subject is rather pathetic - I've written a number of games over the years, and adapted others, but I am not into the high video imaging that others dolt on. But my primary focus and expertise is in data processing and inferencing from the sata sets that I build and process. I also wear several hats - LAN support (three status centers in three locations, and over a hundred local machines, plus the network), and systems analyst (working with another analyst, we resolved and fixed network and telecommunications problems involving numerous federal agencies and saved the company over 100 million dollars in the span of three years).
So some putdown about not having written some computer game hardly makes a dent in my skin. But it shows the person making that comment is unwilling to stay with the facts and would rather resort to personal attacks.
So yes, Kale, you are right. Rude, insulting, and demeaning. And apparently too dense to recognize it when it is pointed out to them, Or maybe too childish by nature to admit it.
You have been right on concerning the unmistakable rudeness that a few choice individuals have shown, and trying to make the point that I haven't written a game so I'm hardly qualified to speak on some subject is rather pathetic - I've written a number of games over the years, and adapted others, but I am not into the high video imaging that others dolt on. But my primary focus and expertise is in data processing and inferencing from the sata sets that I build and process. I also wear several hats - LAN support (three status centers in three locations, and over a hundred local machines, plus the network), and systems analyst (working with another analyst, we resolved and fixed network and telecommunications problems involving numerous federal agencies and saved the company over 100 million dollars in the span of three years).
So some putdown about not having written some computer game hardly makes a dent in my skin. But it shows the person making that comment is unwilling to stay with the facts and would rather resort to personal attacks.
So yes, Kale, you are right. Rude, insulting, and demeaning. And apparently too dense to recognize it when it is pointed out to them, Or maybe too childish by nature to admit it.
has-been wanna-be (You may not agree with what I say, but it will make you think).
Apology Accepted
And I likewise apologize for being overly critical in my comments. I bashed my little finger between two cement blocks, losing most the skin on my finger pad, and that has bothered me all day. But it only hurts me when I type.
has-been wanna-be (You may not agree with what I say, but it will make you think).