|author||Boris Kolpackov <firstname.lastname@example.org>||2015-01-23 12:31:11 +0200|
|committer||Boris Kolpackov <email@example.com>||2015-01-23 12:31:11 +0200|
Diagnose lack of default constructor in pointed-to objects
Lack of the default constructor will lead to uncompilable generated code.
2 files changed, 10 insertions, 6 deletions
diff --git a/feature/list b/feature/list
index 688c9f0..18ae045 100644
@@ -16,12 +16,6 @@
This could be very useful in data migration code. In fact, need to
add an example in the manual when this is supported.
-! 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?
? Duplicate columns
It can sometimes be useful to map multiple data members to the same
diff --git a/reference/feature/list b/reference/feature/list
new file mode 100644
@@ -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