This whole 'no spaces in the path name' thing smacks of cutting corners. If the operating system supports spaces in the path name and the application purports to run on the target operating system it should then conform with the standards of the target operating system.
As of 4.9.9.2 I will now need to relocate my development files/projects etc. Now call me a stickler (or worse) - but I would have thought that should not have been necessary inorder to sucessfully run what is a minor version update?
Can you please give serious consideration in 4.9.9.3 to bringing back whatever you where using in 4.9.9.1 that seemed to happy allow the use spaces in path names.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The MinGW GCC compiler system that Dev-C++ is written for is a descendant of a Unix legacy tool. GCC relies on spaces as a way to separate command line arguments. Making GCC support spaces will take a considerable amount of work, and the main method of compilation, by use of Makefiles, will become alienated from the rest by usage of spaces as Unix and Linux still do not use spaces in their paths.
It's just that spaces are a legacy from the old operating system days and will be very difficult to get out of as it is just the most convenient character the delimit arguments on the command line
Benjamin Lau
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
"Can you please give serious consideration in 4.9.9.3 to bringing back whatever you where using in 4.9.9.1 that seemed to happy allow the use spaces in path names."
You are under a false impression.
The fact of the matter is that version 4.9.9.1 did NOT happily allow spaces in path names. In fact, I would estimate more than 75% of the errors that we had to deal with here were tracible in one form or another to people installing at one point or the other in a directory with spaces, or storing their projects in such a directory. Many hours of people time was being wasted in clean uninstalls, and a ton of frustration induced in users.
So 4.9.9.2 was simply set up to avoid this by forcing installations in places where such problems would not happen.
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
To add to what Wayne just said, note that you can still put your projects and sources in a path containing spaces. Only the installation path of Dev-C++ is forbidden to have spaces.
Of course, if you used to store your projects somewhere in the Dev-C++ install dir (which is obviously a bad idea) you will need to move them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Of course, that was implicit; but some people are just too stubborn to change or don't have a choice (due to idiotic security consideration at the office). :-)
But on Windows XP, spaces in path are handled better than on previous Windows versions.
Anyway, let me make myself clear, I don't want to look like I encourage people to use spaces in paths. I don't like it and I never do it. :-p
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't use them either. But then again I have to hop between IRIX, Linux, Cygwin and Windows, so cross platform issues are a lot closer to where I live than they may be for many.
I also have an installation philosophy. Unless I know for SURE that its OK to install in a directory other than the one the installer wants, I let the installer choose. The folks that wrote the program generally know better than I where their program works best.
Wayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I felt obliged to thank the Dev-C++ crew for the new release. As a matter of fact I installed it and didn't have any problems derived from the new instalation. BTW, I succesfully installed it on Windows 98 and XP.
I noticed an important improvement in the class browser though: now you can go to the declaration or implementation of the functions accurately! This can save you quite a bit of time scrolling up and down just looking for a function's implementation.
Cheers,
Quidamadiuq
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is it possibl to import Visual C++.net project?
If yes how?
Thank You DevC++ Team!!! Good work!
Regards!
This whole 'no spaces in the path name' thing smacks of cutting corners. If the operating system supports spaces in the path name and the application purports to run on the target operating system it should then conform with the standards of the target operating system.
As of 4.9.9.2 I will now need to relocate my development files/projects etc. Now call me a stickler (or worse) - but I would have thought that should not have been necessary inorder to sucessfully run what is a minor version update?
Can you please give serious consideration in 4.9.9.3 to bringing back whatever you where using in 4.9.9.1 that seemed to happy allow the use spaces in path names.
The MinGW GCC compiler system that Dev-C++ is written for is a descendant of a Unix legacy tool. GCC relies on spaces as a way to separate command line arguments. Making GCC support spaces will take a considerable amount of work, and the main method of compilation, by use of Makefiles, will become alienated from the rest by usage of spaces as Unix and Linux still do not use spaces in their paths.
It's just that spaces are a legacy from the old operating system days and will be very difficult to get out of as it is just the most convenient character the delimit arguments on the command line
Benjamin Lau
"Can you please give serious consideration in 4.9.9.3 to bringing back whatever you where using in 4.9.9.1 that seemed to happy allow the use spaces in path names."
You are under a false impression.
The fact of the matter is that version 4.9.9.1 did NOT happily allow spaces in path names. In fact, I would estimate more than 75% of the errors that we had to deal with here were tracible in one form or another to people installing at one point or the other in a directory with spaces, or storing their projects in such a directory. Many hours of people time was being wasted in clean uninstalls, and a ton of frustration induced in users.
So 4.9.9.2 was simply set up to avoid this by forcing installations in places where such problems would not happen.
Wayne
To add to what Wayne just said, note that you can still put your projects and sources in a path containing spaces. Only the installation path of Dev-C++ is forbidden to have spaces.
Of course, if you used to store your projects somewhere in the Dev-C++ install dir (which is obviously a bad idea) you will need to move them.
> To add to what Wayne just said, note that you can still put your projects and sources in a path containing spaces.
which is just as bad
Of course, that was implicit; but some people are just too stubborn to change or don't have a choice (due to idiotic security consideration at the office). :-)
But on Windows XP, spaces in path are handled better than on previous Windows versions.
Anyway, let me make myself clear, I don't want to look like I encourage people to use spaces in paths. I don't like it and I never do it. :-p
I don't use them either. But then again I have to hop between IRIX, Linux, Cygwin and Windows, so cross platform issues are a lot closer to where I live than they may be for many.
I also have an installation philosophy. Unless I know for SURE that its OK to install in a directory other than the one the installer wants, I let the installer choose. The folks that wrote the program generally know better than I where their program works best.
Wayne
I felt obliged to thank the Dev-C++ crew for the new release. As a matter of fact I installed it and didn't have any problems derived from the new instalation. BTW, I succesfully installed it on Windows 98 and XP.
I noticed an important improvement in the class browser though: now you can go to the declaration or implementation of the functions accurately! This can save you quite a bit of time scrolling up and down just looking for a function's implementation.
Cheers,
Quidamadiuq
Your question is really off-topic for this thread. I encourage you to start a new thread with your question.
Wayne