Given all of the changes when forking from Qt, do all of the containers provide parentage? The documentation is not clear. If most things are now wrappers for STL implementations which have no concept of parentage, then I have to ask . . . do all of these containers assume parentage of the objects they contain? No exceptions, no gotcha's, no "on Thursdays when it rains and Fred's at the keyboard" situations.
I had a comment a comment in the Diamond code near a section like this
Code: Select all
if ( m_settings.m_options.preloadClipper() )
{
fileName = m_settings.syntaxPath() + "syn_clipper.json";
m_syntaxPatterns[fileName] = new SyntaxPatterns( fileName );
}
Code: Select all
class SyntaxPatterns
{
CS_GADGET( SyntaxPatterns )
public:
SyntaxPatterns( QString fileName );
SyntaxPatterns( const SyntaxPatterns &patterns );
SyntaxPatterns &operator = ( const SyntaxPatterns &other );
QStringList key_Patterns;
QStringList class_Patterns;
QStringList func_Patterns;
QStringList type_Patterns;
QStringList constant_Patterns;
QString commentSingle;
QString commentStart;
QString commentEnd;
QString pattern_file;
bool ignoreCase;
private:
QByteArray readSyntaxFile();
};
Anyway, I would like some clarification/documentation on this issue.
Thank you.