daily-email: add 2023-05-18
This commit is contained in:
		
							parent
							
								
									b3c4dd21f6
								
							
						
					
					
						commit
						8b97e8c899
					
				
					 1 changed files with 17 additions and 0 deletions
				
			
		
							
								
								
									
										17
									
								
								src/content/daily-email/2023-05-18.md
									
										
									
									
									
										Normal file
									
								
							
							
						
						
									
										17
									
								
								src/content/daily-email/2023-05-18.md
									
										
									
									
									
										Normal file
									
								
							|  | @ -0,0 +1,17 @@ | |||
| --- | ||||
| title: > | ||||
|   Why is backward compatibility important? | ||||
| pubDate: 2023-05-18 | ||||
| permalink: > | ||||
|   archive/2023/05/18/why-is-backward-compatibility-important | ||||
| tags: | ||||
|   - software-development | ||||
| --- | ||||
| 
 | ||||
| In yesterday's email, I mentioned that deprecating code allows it to be backwards compatible - but what does that mean? | ||||
| 
 | ||||
| If I were to remove a function like `drupal_set_message()` that is used code elsewhere in an application, the code would no longer work and would break. | ||||
| 
 | ||||
| As a module or library maintainer, I don't want to cause applications to break by making backward incompatible changes (a "BC break" or a "breaking change"). | ||||
| 
 | ||||
| Maintaining backward compatibility means that people who use the code can update to the latest version without breakages, and if they use any deprecated code, they know to update it to be compatible with future versions. | ||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue