<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div class="y_msg_container"> <hr size="1"><font face="Arial" size="2"><b><span style="font-weight:bold;"></span></b></font>I think there are three ways that this could go:<br><br>- Try to preserve source compatibility for common cases, making porting from TagLib 1 to TagLib 2 as easy as possible<br><br>- Allow all API cleanups now since TagLib 1 is now almost 10 years old and the TagLib 1 to 2 transition will be the last chance for API breakage for probably a very long time<br><br>- Do like Qt often does in major version changes and include compatibility functions in the API that are marked as
deprecated.<br><br>Thoughts?<br><br>-Scott<br>_______________________________________________<br><br>My thoughts ...<br><br>I don't like change, However I also understand progress.<br><br>So, I like the Qt way in a minimalistic fashion, it doesn't hinder progress, it allows easier migration, unfortunately a bit more work for the team!<br><br>-Enjoy<br>fh : )_~<br></div> </div> </div> </div></body></html>