pointPatchFields: Removed all pointPatchFields requiring user specified data from the null-constructor table
This avoids potential hidden run-time errors caused by solvers running with boundary conditions which are not fully specified. Note that "null-constructor" here means the constructor from patch and internal field only, no data is provided. Constraint and simple BCs such as 'calculated', 'zeroGradient' and others which do not require user input to fully specify their operation remain on the null-constructor table for the construction of fields with for example all 'calculated' or all 'zeroGradient' BCs. Following this improvement the null-constructors have been removed from all pointPatchFields not added to the null-constructor table thus reducing the amount of code and maintenance overhead and making easier and more obvious to write new pointPatchField types.
This commit is contained in:
@ -61,13 +61,6 @@ public:
|
||||
|
||||
// Constructors
|
||||
|
||||
//- Construct from patch and internal field
|
||||
${typeName}FixedValuePointPatch${FieldType}
|
||||
(
|
||||
const pointPatch&,
|
||||
const DimensionedField<${TemplateType}, pointMesh>&
|
||||
);
|
||||
|
||||
//- Construct from patch, internal field and dictionary
|
||||
${typeName}FixedValuePointPatch${FieldType}
|
||||
(
|
||||
|
||||
Reference in New Issue
Block a user