Internal and Expanded - Revision history

Manus at 21:02, 23 March 2010

2010-03-23T21:02:50Z

← Older revision		Revision as of 21:02, 23 March 2010
Line 29:		Line 29:

	'''cons''': very inefficient		'''cons''': very inefficient

			==Convenience routine==
			The runtime is equipped with a function that given an object gives you a properly typed TUPLE which contains all the fields of an expanded type. This TUPLE can also be then used to saved back to the expanded field.

			'''pros''': ???

			'''cons''': Still memory inefficient.

	==Extra fields==		==Extra fields==

Manus: /* Extra fields */

2010-03-23T19:01:00Z

Extra fields

← Older revision		Revision as of 19:01, 23 March 2010
Line 52:		Line 52:
	'''pros''': as efficient as the implementation when not using expanded objects.		'''pros''': as efficient as the implementation when not using expanded objects.

	'''cons''': a little bit more complicated to implement since we need to expose some information that are strictly not need by our runtime, so we will have to duplicate some data.		'''cons''': a little bit more complicated to implement since we need to expose some information that are strictly not need by our runtime, so we will have to duplicate some data. If an expanded type have a cycle, we won't follow the cycle and thus we will be back to the normal way of settings the expanded.

Manus: /* Extra fields */

2010-03-23T18:58:02Z

Extra fields

← Older revision		Revision as of 18:58, 23 March 2010
Line 51:		Line 51:

	'''pros''': as efficient as the implementation when not using expanded objects.		'''pros''': as efficient as the implementation when not using expanded objects.

	'''cons''': a little bit more complicated to implement since we need to expose some information that are strictly not need by our runtime, so we will have to duplicate some data.		'''cons''': a little bit more complicated to implement since we need to expose some information that are strictly not need by our runtime, so we will have to duplicate some data.

Manus: /* Nothing special */

2010-03-23T18:57:55Z

Nothing special

← Older revision		Revision as of 18:57, 23 March 2010
Line 27:		Line 27:

	'''pros''': simple		'''pros''': simple

	'''cons''': very inefficient		'''cons''': very inefficient

Manus: /* Extra fields */

2010-03-23T18:41:21Z

Extra fields

← Older revision		Revision as of 18:41, 23 March 2010
Line 48:		Line 48:

	Clearly the thrid option is what is enough, however it would break existing code relying on the presence of ''b''. So we will offer the second variant with a flag to say if the field was an extra field or not.		Clearly the thrid option is what is enough, however it would break existing code relying on the presence of ''b''. So we will offer the second variant with a flag to say if the field was an extra field or not.

			'''pros''': as efficient as the implementation when not using expanded objects.
			'''cons''': a little bit more complicated to implement since we need to expose some information that are strictly not need by our runtime, so we will have to duplicate some data.

Manus at 18:39, 23 March 2010

2010-03-23T18:39:06Z

← Older revision		Revision as of 18:39, 23 March 2010
Line 4:		Line 4:
	To make the discussion consistent, let's suppose we have the following set of classes:		To make the discussion consistent, let's suppose we have the following set of classes:

	<~~code~~>		<e>
	class A		class A
	feature		feature
Line 21:		Line 21:
	sc: STRING		sc: STRING
	end		end
	</~~code~~>		</e>

	==Nothing special==		==Nothing special==
Line 30:		Line 30:

	==Extra fields==		==Extra fields==
	The attributes of the expanded are also visible as extra fields of the object. In other words		The attributes of the expanded are also visible as extra fields of the object. In other words, we would see for class A either one of the following:
			#All components:
			#* b
			#* b.c
			#* b.c.sc
			#* b.sb
			#* sa
			#All first level components and then only necessary components:
			#* b
			#* b.c.sc
			#* b.sb
			#* sa
			#Necessary components:
			#* b.c.sc
			#* b.sb
			#* sa

			Clearly the thrid option is what is enough, however it would break existing code relying on the presence of ''b''. So we will offer the second variant with a flag to say if the field was an extra field or not.

Manus at 18:32, 23 March 2010

2010-03-23T18:32:22Z

@@ Line 1: / Line 1: @@
 [[Category:Persistence]]
 We are discussing here how to export the description of expanded fields in a normal object to enable a fast and efficient introspection of objects at runtime. We will describe the various possibilities the last one being the implementation we have chosen in EiffelStudio.
 ==Nothing special==

Manus: New page: Category:Persistence We are discussing here how to export the description of expanded fields in a normal object to enable a fast and efficient introspection of objects at runtime. We w...

2010-03-23T18:22:04Z

New page: Category:Persistence We are discussing here how to export the description of expanded fields in a normal object to enable a fast and efficient introspection of objects at runtime. We w...

New page

[[Category:Persistence]]
We are discussing here how to export the description of expanded fields in a normal object to enable a fast and efficient introspection of objects at runtime. We will describe the various possibilities the last one being the implementation we have chosen in EiffelStudio.

==Nothing special==