PR# 19585 Obsolete feature INTERNAL.type_name

Problem Report Summary
Submitter: gobobe
Category: EiffelBase
Priority: Low
Date: 2019/10/02
Class: Bug
Severity: Serious
Number: 19585
Release: 19.08
Confidential: No
Status: Closed
Responsible:
Environment: win
Synopsis: Obsolete feature INTERNAL.type_name

Description
Feature `INTERNAL.type_name` as been marked as obsolete. But `INTERNAL.type_name_32` is not available on 19.05, which makes it impossible to have code which compiles both with 19.05 and with 19.08 without any obsolete warnings.

Please consider adding `INTERNAL.type_name_32` in at least one official release before marking  `INTERNAL.type_name` as obsolete.

--
Eric Bezault
To Reproduce

										

									

								

							

						

					

				

			

		

	









	

		

			
Problem Report Interactions

			

				

					
					

						

							
							

								

									
									
										

											

									
											From:gobobe   
											Date:2020/01/15   
																							Status: Closed   
											
											Download   
										

										

                                            
											
										 	
Fixed in 19.12.

											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:gobobe   
											Date:2019/10/08   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
Sounds good to me.
With a possible option in the Code Analyzer to get these warnings anyway if someone wants to see them ahead of time.

--
Eric Bezault

											
											
											

											
										

									

								

							

							
							

								

									
									
										

											

									
											From:alexk_es   
											Date:2019/10/08   
																							Status: Analyzed   
											
											Download   
										

										

                                            
											
										 	
To keep track of obsolete features in the code rather than somewhere else, what about suppressing the obsolete call warning when the corresponding obsolete message has a time stamp in the future?

With such a convention, it would be possible to keep the obsolete mark for `type_name`. If the time stamp would be set to [2020-05-31], the warning would not be reported by EiffelStudio 19.11 until June 2020. This should give sufficient time for migration to the new version of EiffelStudio.

The exact convention about the grace period could be discussed a bit deeper if needed.