When I go to gcc's web site https://gcc.gnu.org/, I see 3 current versions: 5.5, 7.2, and 6.4. Unfortunately, there's no explanation anywhere I could see of what the differences between the three might be. One would expect that 7.2 would be the most recent but that doesn't appear to be the case, as they are all relatively recent (in fact 5.5 is more recent than 7.2). Does anyone know what the differences are and why one might be preferable to the others?
thanks
Major versions add new features. Minor versions fix bugs. If a bug is found in an earlier major version, a new minor version is released to fix it.
Related
I was taking a look at https://gcc.gnu.org/releases.html and saw that the GCC version numbers aren't increasing monotonically with respect to the date unlike most products where the most recent version has the largest version number.
e.g., GCC 8.5 was released 5/14/21, and 11.1 4/27/21.
Why are the version numbers for gcc structured this way?
Based on reading how they format their version numbers, it seems like its because each major release ends up as a branch with their own number of fixes rather then features. There may be reasons on why you would want to stay on the 8.x branch rather then 11.x branch due to compatibility issues, which is why they release fixes for older branches. You can read more here. Hopes this helps clear things up!
I upgraded to php7.4 on my dev box and am receiving a lot of deprecated errors with Propel 1.7.2. I see there is a closed thread in the support channel indicating fixes are in master, but they sure haven't made it to Propel 1.7.3 at http://propelorm.org/Propel/download.html. Does anyone know if/when the Propel folks are going to release a 1.7.x that is compatible with php74 (php 7.4)?
I wouldn't expeced to much from propel. The Project is more or less dead as of March 21.
As of their official github-page propel1 is outdated and unmaintained. See: https://github.com/propelorm/Propel
Current stable (and outdated and unmaintained) version of Propel -
Please use v2 https://github.com/propelorm/Propel2
Propel2 on the other hand is still in alpha. See: http://propelorm.org/download.html
Note: The version 2 of Propel is still under development. Please visit
http://propelorm.org/Propel/ if you want to use a stable version.
There is also Propel3. Which is not even in alpha yet. See: https://github.com/propelorm/Propel3
Propel3 is an open-source Object-Relational Mapping (ORM) for modern
PHP 7.1+. Version 3 of Propel ORM replaces Propel2, which is not
maintained anymore.
Maybe also see the discussion here: https://github.com/propelorm/Propel3/issues/92
I have a utility service x which is in maven repo and is used by some of my other services. We normally update the minor version of the service x when we make small changes and we are currently on version 1.0.15.
No I am making another change and I was thinking whether I should update version to 1.0.16 or I should update the version like 1.1.0.
If anyone can provide an explanation on how this should be done in general, that would I am sure help other developers as well as me. Please let me know if you need further information.
Different projects follow different standards on this, so follow what the repository has done to date.
A well-regarded standard for this is called Semantic Versioning (https://semver.org/). If you are starting a new project or there isn't a standard already in place, I would recommend using this.
Semantic Versions are in the format: MAJOR.MINOR.PATCH.
If you have fixed a bug: increase the patch version
If you have introduced new functionality in a non-breaking way: increase the minor version (and reset patch to 0)
If you have introduced breaking changes: increase the major version (and reset the patch and minor version to 0).
If you are unsure whether your change is a breaking change or not - consider your package (or API) from its consumers' perspectives. If their code has to change as a result of your change then it's a breaking change.
We have latest Xcode(7.2) having Swift(2.1.1) installed in few mac systems. Here developer didn't find any errors in his code which was checked in, but the same code used at other end were observing errors(most of them related unwrapping variables).
verified all settings and version details not able to find any difference. Any help or suggestions will be appreciated. Thanks
Most likely the machine "at the other end" is not running Xcode 7.2. There is a tool for converting Swift 1.x to 2.x, but not the other direction. But without code sample illustrating the problem, we can't help you much. In addition to shifting unwrapping conventions, there is new syntax later versions of Swift (e.g. guard, error throwing, etc.).
But, if you're going to share a Swift project amongst multiple developers, you probably just want to make sure everyone is using the same version of Xcode. And with Swift progressing as quickly as it is, you might want to encourage everyone to use the latest production version of Xcode.
I am having some real issues with Magento version 1.4, I get alot of "There has been an error processing your request." errors do you think going to the latest version of 1.3 would be more stable ?
No, based on the information you've given, there's no reason 1.3 or 1.4 will run any more, or less stable for you. Track down the reasons for the error message (in your PHP/Apache/Magento error log. Once you know why the application is failing, you'll have a better idea if it's something specific to 1.4, or something about your general server setup.
I would disagree with Alan on this one, that is if your question is only if 1.3 (1.3.3) is more stable than 1.4. Since 1.3 has been around a lot longer, hand multiple sub-releases, etc., I think you'll find more stability in 1.3.3 than you would with 1.4.
If your question was whether or not to go with 1.3 or 1.4, I would definitely suggest going with 1.4. You may want to tackle whatever might be causing your errors, as it could be something rather simple. I have been using 1.4 since it came out, and developing pretty heavily with it, and I don't think I've gotten the error you are getting at all. In fact, I don't think I have had any issues whatsoever. There are known issues in upgrading to 1.4, but other than that, I have enjoyed it quite a bit.
The best to do would be to look at the error reports in var/reports/ and look at the exact error. That's not really a question of stablelity between the two versions.