|
No, the other way round. The variable declared in the method will be the one that is used, as it is in the innermost scope. But you should not be declaring the same variable at two scope levels. Just change your code as I suggested to correct the problem. As to the index problem, i suggest you change the do while to a simple while or for loop, to ensure you do not enter the loop if information_main.count() returns zero.
|
|
|
|
|
So in other words "index" in constructor and "index" in methods are independent , hence not source of the "out of range error".
That should apply to any variable, including template.
I understand that using same names could be buggy, but I need to verify WHAT is causing the
"out of range error" and IMHO using DIFFERENT names should not be "real " solutions, unless something else is wrong with my implementation of templates.
As I said - this is a test code and the "count" is used to simply verify the list content prior to doing the "do -while " loop and it is > 0.
I have never used "iteration" but planning to employ it after I get the "out of range " error Solved.
|
|
|
|
|
Having this;
QList<QBluetoothHostInfo> information_main; inside the method creates a new Qlist type variable called 'information_main', this variable is totally different than the class variable called 'information_main' that has been initialized in a class constructor. This new QList variable (the one just declared inside the method) is empty because you just created it and have not added anything to it. When you make an indexed access to an empty QList variable it will fail. That's why you have to initialize (add stuff to) the new QList variable (the one just declared inside the method) to get the loop to work.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Yes, as I mentioned above the one in the innermost scope is the one that will be used; that is the one declared inside the method. But you really should not create variables with the same name like this, it just confuses people, particularly you. See my last sentence in the previous reply for a possible fix to the out of range error. But you should really capture the count first in a variable and test it to see if it returns a ositive value.
|
|
|
|
|
I am not sure who is confused. Just read the original post and subsequent comments.
So far it looks as the template code fails if there are NO items in it. That makes sense, but it is not the primary issue - just nice to know.
However, the list is not empty and I still do not have an answer to the original post.
Maybe I should rephrase the question.
The template list content was created by other process, what I want is to read it - I do not want to rebuild / reinitialize it.
I can read it fine first time in constructor, now I like to read it again in method.
I do not want to reinitialize it.
And I am doing it wrong , and the matching names is NOT the issue.
I do not want to reinitialize it.
|
|
|
|
|
Member 14980433 wrote: I am not sure who is confused.
I am, because there is still some information missing. And I cannot understand why you need to read this information inside the constructor (which is definitely wrong), as well as in the method (which is correct).
But to go back to the main point, the only way to resolve the index out of range problem is to use the debugger and step through the code as it runs.
|
|
|
|
|
Is there a chance that the following call
QBluetoothLocalDevice::allDevices(); may return no devices? If so, your do-while loop will have an out of range issue.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Thanks for the reply.
Good point, but does not address the question.
The do-while-loop compares the index to count of the items being processed.
No count , no processing,
Yes, I could check the count before entering the loop.
I am sure I will find more "elegant" way to process the items and stop the loop.
|
|
|
|
|
Member 14980433 wrote: No count , no processing,
No, you're going to process it once before size is checked, and likely crash if the list is empty.
Member 14980433 wrote: I am sure I will find more "elegant" way to process the items and stop the loop.
Indeed, most likely a for loop.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
No, you're going to process it once before size is checked, and likely crash if the list is empty.
My objective is to identify the reason for the "out of range "error.
I am getting same when accessing another template list.
Ok, let's make an assumption the do-while " list " is indeed empty. ( It is not )
Would the compiler produce the "index out of range" error then ?
|
|
|
|
|
It is not the compiler that produces the error, it is your code when it runs. You really need to make use of the debugger to find out exactly where the error occurs and what variable values are the cause.
|
|
|
|
|
Member 14980433 wrote: Ok, let's make an assumption the do-while " list " is indeed empty. ( It is not )
Why are you sure it is non-empty?
How did did you check it? Using debugger? Using TRACE with the item count? Using something else?
|
|
|
|
|
This thread is not very productive.
Please do not waste your time "taking side trips" , perhaps re-read the original EDITED post
to concentrate on the real issue.
I am using the templates wrong and have no idea why.
Thanks for understanding.
|
|
|
|
|
Firstly this is not a template, it is (one assumes, since we cannot see you code) a class. And a number of us have explained at length what is wrong and how to fix it. If you think that is taking side trips ...
|
|
|
|
|
Member 14980433 wrote: Template "list" = QBluetoothLocalDevice::allDevices();
It would be nice if contributions lead to resolve this SPECIFIC problem.
Naming variables, verifying validity of "loop index / count" , pointing out the code is
repeated in class method so far does not addresses my error usage of template.
Did you use the Debugger to check what this
QBluetoothLocalDevice::allDevices(); returns?
|
|
|
|
|
Why complicate things??
Is it not sufficient that I get run time error?
Running debug is still not addressing the issue.
Logically - if the "list count " is > 0 the code in constructor works.
I did verify the count > 0 before do-while loop , but that is superficial.
If same code is used in method it appears that the count changed - the run time error said so.
Hence using debugger will just confirm that - so what is the point? ( another useless side trip, in my opinion, proving nothing ).
I will repeat - did I used the template QList wrong is my concern? How did the contents of the list changed AKA index is no longer valid ?
I will delete the code in constructor and run only the method code. That is my next best guess, but it will NOT answer the problem.
|
|
|
|
|
Member 14980433 wrote: Running debug is still not addressing the issue.
Of course it is. That is what the debugger provides: information about why your program crashes, raises an exception, produces the wrong output etc. But if you want to waste your time complaining because we cannot magically produce the answer that you think you deserve, despite having only half the picture, that is up to you.
|
|
|
|
|
It absolutely is the issue.
The debugger is there to debug YOU, not the code. It's there to show you what the code is really doing compared to what you THINK it does.
|
|
|
|
|
Member 14980433 wrote: If same code is used in method it appears that the count changed - the run time error said so.
Hence using debugger will just confirm that - so what is the point? ( another useless side trip, in my opinion, proving nothing ).
I will repeat - did I used the template QList wrong is my concern? How did the contents of the list changed AKA index is no longer valid ?
Just debug your code step-by-step, look in the debug/watch window, compare the variables values with the ones you expected to see,... And you will find the problem!
|
|
|
|
|
Could you post your class definition and the whole of your method?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Not sure if I want to do so.
So far the discussion is centered on "why are you doing this ?" instead of on resolution.
My code is written for me and I have had bad experience of "gurus" criticizing my style.
Do not want that again.
Let me try my last idea - running just the method and I'll try to sanitize / remove my comments from he code.
Fair?
|
|
|
|
|
Don't know what to tell you, showing code is far better than trying to describe it. No one has criticized your coding 'style', they've mentioned things that are logical improvements, not code style improvements. Make the smallest runnable example that exhibits the problem, then show the whole example.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Here is a working , sanitized / abbreviated TEST code used in method
information_main.count() = 2
{
QList<QBluetoothHostInfo> information_main = QBluetoothLocalDevice::allDevices();
int index = 0;
do
{
information_main.at(index).address().toString();
index++;
} while( index != information_main.count() );
reset index and run it again - works as expected
fails run time if index is not reset - as expected
index = 0;
do
{
information_main.at(index).address().toString();
index++;
} while( index != information_main.count() );
|
|
|
|
|
What is this? Can't you post the whole class definition, initialization, and the method you mentioned? 
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
What does this have to do with the problem? You were asked to create a sample that demonstrates the problem you are having. This merely demonstrates that correct management of the index variable makes the code work.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
