It always hurts when there is no universal solution. Only the void stands out like that.
That's why instead of void it's better to make bool ... return(true) or something similar but not a ugly code type. Why they have created such a freak (no flexibility at all) is unclear.
when opening in excel I have to go through the delimiter recognition procedure all the time... even if it's UTF-8 the file is still created in UTF-16...
//+------------------------------------------------------------------+ class A { public: virtual int Test_A() { return 100; } }; //+------------------------------------------------------------------+ class B :public A { public: virtual int Test_A() { return 200; } };
B b; //+------------------------------------------------------------------+ void OnStart() { Comment (A::b.Test_A()); } //+------------------------------------------------------------------+
Inside B is like this
A::Test_A()
you can call the parent method.
And if you need it outside, then only through pointer casting. This is what virtual functions are made for, to be substituted depending on class type.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Two macros don't seem to hurt much.
It always hurts when there is no universal solution. Only the void stands out like that.
That's why instead of void it's better to make bool ... return(true) or something similar but not a ugly code type. Why they have created such a freak (no flexibility at all) is unclear.Guys, please what else needs to be added here:
to create a normal csv file with UTF-8 encoding,
What am I doing wrong?
Guys, please what else needs to be added here:
to create a normal csv file with UTF-8 encoding,
What am I doing wrong?
What's the problem ?
when opening in excel I have to go through the delimiter recognition procedure all the time...
even if it's UTF-8 the file is still created in UTF-16...
and I don't know how to overcome it...
there's no such problem in 4...
and how to beat it I don't know...
add FILE_ANSI?
add FILE_ANSI?
add or replace?
add FILE_ANSI?
added,
but it's all a bit of a mess...
I want to call the parent method
Here's the code, what am I doing wrong ???
//+------------------------------------------------------------------+
class A
{
public:
virtual int Test_A()
{
return 100;
}
};
//+------------------------------------------------------------------+
class B :public A
{
public:
virtual int Test_A()
{
return 200;
}
};
B b;
//+------------------------------------------------------------------+
void OnStart()
{
Comment (A::b.Test_A());
}
//+------------------------------------------------------------------+
Inside B is like this
you can call the parent method.
And if you need it outside, then only through pointer casting. This is what virtual functions are made for, to be substituted depending on class type.
And if you need to go outside, only through pointer casting
It always hurts when there is no one-size-fits-all solution. Only void stands out like that.
I won't write what is possible, otherwise it may turn out to be simple again and pavlick_ will ...lick_ again