- Forum
- General C++ Programming
- Having Variables in Identifiers
Having Variables in Identifiers
How do I put variables (in this case, x) into identifiers (such as ArmoryLocker*, where * is a predetermined number)?
I have underlined all the variables added to identifiers.
I have underlined all the variables added to identifiers.
|
|
You can't.
When your code is compiled and turned into an exe, the variable names don't really do anything anymore. If you build in Release mode (at least in VS), then I don't think that variable names are retained. Therefore identifying or editing variable names at runtime (while the program is running) is impossible.
What you CAN do is make ArmoryLocker an array.
Example:
When your code is compiled and turned into an exe, the variable names don't really do anything anymore. If you build in Release mode (at least in VS), then I don't think that variable names are retained. Therefore identifying or editing variable names at runtime (while the program is running) is impossible.
What you CAN do is make ArmoryLocker an array.
Example:
|
|
Last edited on
Alright, I can see how that would work.
But I've never been very good with arrays. One line, as in my code, was easy enough to understand, but something like that I wouldn't even know where to begin with defining it. Perhaps I'm just too tired to work it through, so how would defining
Specifically, how would it fit into
I only have 3 useable lockers, so I don't want to have to repeat that check more than that. I'm trying to avoid as much repetition as I can get.
The code I have now (with the x variable that I now know is pointless) I boiled down from 3 lengthy checks where x was actually 1, 5, and 8 for the 3 different instances.
But I've never been very good with arrays. One line, as in my code, was easy enough to understand, but something like that I wouldn't even know where to begin with defining it. Perhaps I'm just too tired to work it through, so how would defining
Inventory ArmoryLocker[8] be put into the checks for items?Specifically, how would it fit into
|
|
I only have 3 useable lockers, so I don't want to have to repeat that check more than that. I'm trying to avoid as much repetition as I can get.
The code I have now (with the x variable that I now know is pointless) I boiled down from 3 lengthy checks where x was actually 1, 5, and 8 for the 3 different instances.
I would replace your code with:
|
|
If I'm not mistaken, that would output every item in all lockers at once.
I believe I found a way around the problem by locking the values into temporary variables, then setting the values to 0. On exiting a locker, any items that remain are put back into their values and the temporary variables are set to 0 again.
The code is about 100 lines longer, but that's still over 250 lines shorter than when I started.
The important bits:
# is a set value, 1, 5, or 8. This code repeats 3 times in
I may eventually change this to a for loop as suggested, where _ is the same number as # through a single variable. This will lead to many more variables, but will accomplish the same goal without repeating code.[/b]
I believe I found a way around the problem by locking the values into temporary variables, then setting the values to 0. On exiting a locker, any items that remain are put back into their values and the temporary variables are set to 0 again.
The code is about 100 lines longer, but that's still over 250 lines shorter than when I started.
The important bits:
# is a set value, 1, 5, or 8. This code repeats 3 times in
else if statements for each locker.I may eventually change this to a for loop as suggested, where _ is the same number as # through a single variable. This will lead to many more variables, but will accomplish the same goal without repeating code.[/b]
|
|
|
|
|
|
|
|
Last edited on
I would be tempted to consider something along these lines:
|
|
Then something like this:
Can be reduced to this:
|
|
Can be reduced to this:
|
|
Last edited on
You wouldn't even need
I'm guessing that
I'm also still a bit confused about the variables in the identifiers. It didn't work the way I was trying to do it (I switched the brackets out for parentheses), so I figured it was because it had to wait for user input. Yet your example does the same. What is the difference? Maybe I'm reading it wrong.
Edit: At any rate, I was too lazy to reconfigure my entire inventory system to account for a single array declaration, so instead I just used your idea to make Inventory Empty and Temp to replace the temporary variables and the long list of setting everything equal to 0. Cut down quite a lot.
int Item_Types or the 10th 0 in the array, from the looks of that. Let me fiddle around with that idea and see how it turns out. A reduction like that would be very significant.I'm guessing that
Inventory x takes the array { 0, 0, 0, 0, 0, 0, 0, 0, 0 } and puts each one into HIMi, then HI, then HIMa, and so on? I've never really done a whole lot with arrays, but they're a good addition.I'm also still a bit confused about the variables in the identifiers. It didn't work the way I was trying to do it (I switched the brackets out for parentheses), so I figured it was because it had to wait for user input. Yet your example does the same. What is the difference? Maybe I'm reading it wrong.
Edit: At any rate, I was too lazy to reconfigure my entire inventory system to account for a single array declaration, so instead I just used your idea to make Inventory Empty and Temp to replace the temporary variables and the long list of setting everything equal to 0. Cut down quite a lot.
Last edited on
Topic archived. No new replies allowed.