Then how will you know if it should changed or not? If I want to change a variable case, I just do it and they all change. Your way, you would have to assign that case to the first time the variable was used in the program. What if that first use gets erased? You would also have to make the IDE remember each variable case in this scenario. Personally, I don't care about this issue either way. If I had to choose, I like the new method a bit better but not if it means more work because of what I just brought up. Pete |
| Response Title | Author and Date |
| * LOL, that will not be a problem. You UCASE EVERYTHING! | on Apr 18 |
| Then you are DIM'ing it implicitly just by using the variable for the first time | on Apr 18 |
| DIM lol AS STRING: PRINT UCASE$(lol) | on Apr 19 |
| MUST I OPTIMIZE EVERYTHING YOU DO? | qbguy on Apr 19 |
| * BYTE ME :) | on Apr 19 |
| QuickBASIC could never replace Python | Y2K = 2048 on Apr 20 |
| What bad programming practices? | qbguy on Apr 21 |
| Regarding not declaring variables in Python... | RpgFan on Apr 21 |
| I can think of some languages that let you use variables uninitialized | Dean Menezes on Apr 22 |
| * What does this have to do with QB64? | on Apr 22 |
| It is a response to rpgfan's post about python not allowing uninitialized variables | qbguy on Apr 22 |
| * Why would you want it to? | on Apr 22 |