Sorry, the standard gcc also has an error, it's not in my test one, which I compiled myself disabling part of the strict control and forgot to kill it in the paths )))
Before publishing the code in kodobase, do the authors purposely stuff the source code into 1-3 files, or do most of the submitted authors write "everything in a pile" that way?
Are the indexes constant?
indexes are numeric: 1 2 3 ... It is implied that in place of A<int> there can be const A<int> as well.
indexes are numeric: 1 2 3 ... It is implied that in place of A<int> there can also be const A<int>
In this case a[ 0 ] = a[ 1 ]; should an error be generated?
In this case a[ 0 ] = a[ 1 ]; should it give an error?
{
A<int> a;
const A<int> b;
a[ 0 ] = b[ 0 ]; //нормально
b[ 1 ] = a[ 2 ]; //ошибка
}
Chrome must have glitched. Try using IE.
And what function does gcc call in the end?
How do you determine if a chart is completely invisible (cluttered with other charts or minimised)?
I want to disable the calculation visual part when it's really not needed. To offload the CPU.
How do you determine if a chart is completely invisible (cluttered with other charts or minimised)?
I want to disable the calculation visual part when it's really not needed. To offload the CPU.
interesting question
How do you determine if a chart is completely invisible (cluttered with other charts or minimised)?
I want to disable the calculation visual part when it's really not needed. To offload the CPU.