From 85264a7989a063efba0772560349938b675de4ec Mon Sep 17 00:00:00 2001
From: Oleg Subbotin See BDE 3.127.0 Release for more information. Dec 6, 2023 See BDE 3.126.0 Release for more information. Nov 10, 2023 See BDE 3.125.0 Release for more information. Oct 9, 2023What is BDE?
BDE Latest News¶
+BDE 3.127.0 Release¶
+
+
+BDE 3.126.0 Release¶
+
+
+BDE 3.125.0 Release¶
+
+
+BDE 3.124.0 Release¶
diff --git a/knowledge_base/coding_standards.html b/knowledge_base/coding_standards.html
index 0ef2f0fbeb..8977a96d5d 100644
--- a/knowledge_base/coding_standards.html
+++ b/knowledge_base/coding_standards.html
@@ -42,7 +42,7 @@
-
+
@@ -269,7 +269,7 @@
Next
- Previous
+ Previous
5.6.1
+++Any include directives used by the test driver that refer to components in +the same package and not otherwise used by the component itself must appear +in the component’s implementation file and appended with the comment:
+++++// for testing only +
The for-testing-only include directives must not introduce any cycle of +physical dependency into the package (see Rule 3.1.8) and +must be sorted alphabetically with include directives of other components +from the component’s package, if any (Rule 4.3.5).
+Note: To maximize the potential for re-use, component authors should aim +for a component to have as small a set of dependencies as can be reasonably +achieved, including for-testing-only dependencies. The
+// for testing +only
comment serves to highlight when additional dependencies are added to +a component through testing.
+ |
Redundant include guards must not be used in the implementation file.
+The requirement to append the
+// for testing only
labels serve to remind +developers that such additions may adversely effect the reuse of the +component and explain their presence to future developers (or automated +tools) lest those directives be deemed superfluous as they are not required +by the component itself.By adding testing-only dependencies to those of the component itself, we +ensure that such dependencies do not introduce cycles. Avoiding any +test-driver introduced cycles enables a bottom-up testing strategy such that +tests for a component can be written in terms of lower-level components that +have been tested independently.
++
++ + ++ + + +
XML: balxml.
BER: balber_berdecoder and balber_berencoder.
BDE externalization format: bslx.
BDE externalization format: bdex.
Python ( only for BDE wrappers )
pkg-config
( For external dependencies resolution )
Note
+pkg-config
is required to resolve external build dependencies for
+the high level BDE libraries. This tool is not required to build
+bde
itself as it does not have external dependencies.