PR# 19325 Built-in features in WEL_IDENTIFIED

Problem Report Summary
Submitter: gobobe
Category: WEL
Priority: Medium
Date: 2017/02/07
Class: Feature Request
Severity: Non-critical
Number: 19325
Release: 17.01
Confidential: No
Status: Analyzed
Responsible: manus_eiffel
Environment: win
Synopsis: Built-in features in WEL_IDENTIFIED

Description
In class WEL_IDENTIFIED, it's unfortunate that some of the routines are declared built-in. Shouldn't this be reserved for kernel routines?
Especially in that case: why aren't the routines from IDENTIFIED_ROUTINES used (as indicated by the obsolete message) instead of "built_in" for their implementation? 

--
Eric Bezault
To Reproduce

										

									

								

							

						

					

				

			

		

	









	

		

			
Problem Report Interactions

			

				

					
					

						

							
							

								

									
									
										

											

									
											From:gobobe   
											Date:2017/04/06   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
If the problem is with Current in void-safe mode, then I don't think that it is polluting class IDENTIFIED to move them there. I think that these are general purpose routines (not specific to WEL) in void-safe mode.

--
Eric Bezault

											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:manus_eiffel   
											Date:2017/02/09   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
We agree that we should be using the recommendation of the obsolete clause. Unfortunately this would break the compilation of Vision2 as we are not allowed to use Current until it is properly initialized. This is why we use externals for those instead. The reason for builtins is because they are actually runtime routines that require a specific implementation for all our supported platforms. We initially put them in WEL because this is where they are used and we did not want to pollute IDENTIFIED with routines that are only used for a very specific case.

We will look if we can change the Vision2 implementation and change the order of creation to avoid this problem.