
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
This is why I said the std lib is not holy:
This is actually from the CArrayRing buffer class in the codebase, but I do agree that the stdlib isn't gospel.
One final tweak to this in order to include object pointers in the case of setting NONE from templated methods/classes.
This is actually from the CArrayRing buffer class in the codebase, but I do agree that the stdlib isn't gospel.
I meant changing the CObject class.
I meant changing the CObject class.
Oh... I didn't see that you had added the methods to CObject. I'm not sure that I would agree with that because I'm sure there's a lot of descendant classes that already have defined a None method. Also, access to the methods would be limited to subclasses of CObject. This definitely belongs in the global scope so it can be accessed from anywhere.
Oh... I didn't see that you had added the methods to CObject. I'm not sure that I would agree with that because I'm sure there's a lot of descendant classes that already have defined a None method. Also, access to the methods would be limited to subclasses of CObject. This definitely belongs in the global scope so it can be accessed from anywhere.
descendant classes that already have defined a None method.
Call it PyNone to avoid clobbering ?
Just a thought . . .
Maybe I miss something, but if every object has the ability to tell it's decendents what is the None() value of every type they possibly can ask about, why do they need to access another object's None() methods?
Because this abstraction is not limited to CObject descendants.
Call it PyNone to avoid clobbering ?
Just a thought . . .
And I don't even have None methods
Looks like I don't either.
Because this abstraction is not limited to CObject descendants.
For me, it's not relevant.
I am not going to define a dummy CObject just for calling those methods.
It's for OO only.
You mean if you write code outside of class?
For me, it's not relevant.
That's the entire point of this thread. No matter what scope, you should have access to a universal None type of which you can use to initialize any type in order to compare to the same None value. This, of course, is used to avoid collisions with ambiguous values. For example,