Documentation:BDL - Revision history

Jafma: /* Repeated (sequence, array) */

2011-02-16T14:02:37Z

‎Repeated (sequence, array)

2011-02-16T14:01:47Z

‎Repeated: sequence

2011-02-16T14:01:32Z

‎Repeated: sequence

2011-02-16T14:00:20Z

‎Repeated (sequence, array)

2011-02-16T13:59:38Z

‎Repeated (sequence, array)

2009-07-24T18:08:01Z

‎Others: string

2009-07-24T18:06:38Z

‎Others: string

2009-07-24T18:06:02Z

‎Others: string

2009-07-24T18:05:40Z

‎Others: string

2009-07-14T08:19:24Z

@@ Line 120: / Line 120: @@
 </cpp>
-'''NOTE:''' ''Do not use sequences of octects to communicate serialized objects from one module to another: that means that you are forcing any receiver to use the same objects definition, tying them to your needs. Use only sequences of octects to pack together data that either has no structure or its structure is common knowledge -no additional libraries needed to handle it-.''
+'''NOTE:''' ''Do not use sequences of octects to communicate serialized objects from one module to another: that means that you are forcing any receiver to use the same objects definition and software as you, tying other people to your needs. Use only sequences of octects to pack together data that either has no structure or its structure is common knowledge -no additional libraries needed to handle it-.''
 * '''Arrays''': Fixed-length indexed sets of elements of the same type (maybe composed). For example:

@@ Line 463: / Line 463: @@
 === Repeated: sequence ===
-'''NOTE:''' ''''please read the note on sequences in their definition within the BDL language.''''
+'''NOTE:''' ''please read the note on sequences in their definition within the BDL language.''
 The sequences are mapped to C++ classes.

@@ Line 462: / Line 462: @@
 === Repeated: sequence ===
 The sequences are mapped to C++ classes.
@@ Line 504: / Line 506: @@
 (*out_seq)[0] = BABEL::string_dup("my string"); // use (*out_seq)[index] instead of out_seq[index]
 </cpp>
 === Repeated: array ===

@@ Line 120: / Line 120: @@
 </cpp>
-'''NOTE:''' Do not use sequences of octects to communicate serialized objects from one module to another: that means that you are forcing any receiver to use the same objects definition, tying them to your needs. Use only sequences of octects to pack together data that either has no structure or its structure is common knowledge -no additional libraries needed to handle it-.
+'''NOTE:''' ''Do not use sequences of octects to communicate serialized objects from one module to another: that means that you are forcing any receiver to use the same objects definition, tying them to your needs. Use only sequences of octects to pack together data that either has no structure or its structure is common knowledge -no additional libraries needed to handle it-.''
 * '''Arrays''': Fixed-length indexed sets of elements of the same type (maybe composed). For example:

@@ Line 119: / Line 119: @@
 };
 </cpp>
 * '''Arrays''': Fixed-length indexed sets of elements of the same type (maybe composed). For example:
@@ Line 129: / Line 131: @@
 };
 </cpp>
 === Others (enum, string) ===

@@ Line 771: / Line 771: @@
 === Others: string ===
-Strings of BDL are translated into (possibly const) char * of C++ if they appear directly as types of some input/output parameter of a service. They can be also defined as variables in the logic of some service in this way: BABEL::String str;. In both cases, the helper functions described below apply.
+Strings of BDL are translated into (possibly '''const''') '''char *''' of C++ if they appear directly as types of some input/output parameter of a service. They can be also defined as variables in the logic of some service in this way: '''BABEL::String str;'''. In both cases, the helper functions described below apply.
-However, when a BDL string type appears as the type of a field of a composed public type of a module, it is not translated to a BABEL::String type. In that case, it is translated to a special object that can use BABEL::string_dup for assignment, but it cannot use BABEL::string_free for deletion.
+However, when a BDL string type appears as the type of a field of a composed public type of a module, it is not translated into a '''BABEL::String''' type. In that case, it is translated into a special object that can use '''BABEL::string_dup''' for assignment, but it '''cannot''' use '''BABEL::string_free''' for deletion.

← Older revision		Revision as of 18:06, 24 July 2009
Line 773:		Line 773:
	Strings of BDL are translated into (possibly const) char * of C++ if they appear directly as types of some input/output parameter of a service. They can be also defined as variables in the logic of some service in this way: BABEL::String str;. In both cases, the helper functions described below apply.		Strings of BDL are translated into (possibly const) char * of C++ if they appear directly as types of some input/output parameter of a service. They can be also defined as variables in the logic of some service in this way: BABEL::String str;. In both cases, the helper functions described below apply.

−	However, when a BDL string type appears as the type of a field of a public type of a module, it is not translated to a BABEL::String type. In that case, it is translated to a special object that can use BABEL::string_dup for assignment, but it cannot use BABEL::string_free for deletion.	+	However, when a BDL string type appears as the type of a field of a composed public type of a module, it is not translated to a BABEL::String type. In that case, it is translated to a special object that can use BABEL::string_dup for assignment, but it cannot use BABEL::string_free for deletion.

← Older revision		Revision as of 18:05, 24 July 2009
Line 770:		Line 770:

	=== Others: string ===		=== Others: string ===
		+
		+	Strings of BDL are translated to (const) char * of C++ if they appear directly as types of some input/output parameter of a service. They can be also defined as variables in the logic of some service in this way: BABEL::String str;. In both cases, the helper functions described below apply.
		+
		+	However, when a BDL string type appears as the type of a field of a public type of a module, it is not translated to a BABEL::String type. In that case, it is translated to a special object that can use BABEL::string_dup for assignment, but it cannot use BABEL::string_free for deletion.
		+

	'''Helper functions'''		'''Helper functions'''

@@ Line 206: / Line 206: @@
-== Predefined composed types ==
+== Predefined types ==
-A few composed types are predefined so they can be readily used by any BABEL module.
+A few types are predefined so they can be readily used by any BABEL module. Their translation into the generated source code language follows the same rules as though they were defined by the user.
 <cpp>