summaryrefslogtreecommitdiff
path: root/docs/README
diff options
context:
space:
mode:
authorAdam Mitz <mitza-oci@users.noreply.github.com>2010-02-19 15:21:42 +0000
committerAdam Mitz <mitza-oci@users.noreply.github.com>2010-02-19 15:21:42 +0000
commit13229d689ceb4d11d6d8c61691df2caa00406cd0 (patch)
treeac826c340786dcf9389c709b518a20784fe7fd24 /docs/README
parent5e814f1c9faef90b9916fca305a934fa07b6c7e3 (diff)
downloadMPC-Define_Custom_inheritance.tar.gz
adding documentation for the Define_Custom inheritance featureDefine_Custom_inheritance
Diffstat (limited to 'docs/README')
-rw-r--r--docs/README5
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/README b/docs/README
index ad67a3c9..3a23de4a 100644
--- a/docs/README
+++ b/docs/README
@@ -437,6 +437,11 @@ information about how to process the input files and what output files are
created. Once the custom file type is defined, MOC_Files can be defined in
order to specify the input files for this new file type.
+Define_Custom definitions may use single inheritance. This is useful for
+creating aliased names:
+ Define_Custom(QtMOC) : MOC {
+ }
+
Here is a list of keywords that can be used within the scope of
Define_Custom or Modify_Custom: