summaryrefslogtreecommitdiff
path: root/reference/feature/list
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2015-01-23 12:31:11 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2015-01-23 12:31:11 +0200
commit006dd946e550a16004d4b7f62e9e026e4504cd23 (patch)
tree52eabb6c027329a57f0daf1c40be120212dacbb9 /reference/feature/list
parent52785dde4b58f2edacdccf7d8557fdf41cb33781 (diff)
Diagnose lack of default constructor in pointed-to objects
Lack of the default constructor will lead to uncompilable generated code.
Diffstat (limited to 'reference/feature/list')
-rw-r--r--reference/feature/list10
1 files changed, 10 insertions, 0 deletions
diff --git a/reference/feature/list b/reference/feature/list
new file mode 100644
index 0000000..2cc3e8a
--- /dev/null
+++ b/reference/feature/list
@@ -0,0 +1,10 @@
++ Diagnose lack of default ctor if object used in relationship
+
+ Got two questions on the mailing list about that in one week. Maybe
+ always diagnose lack of public ctor? Maybe with a warning if no
+ relationship? The no_ctor pragma like no_id?
+
+ For now only diagnose (error) for pointed-to objects since that
+ will lead to uncompilable generated code (as opposed to user
+ code). Another option would be to add an option to warn about
+ the lack of default ctor in all persistent classes. \ No newline at end of file