Joined: 26 Aug 2004, 07:11 Location: Virginia Tech
haha :)
Yeah, I agree that msoft (zomg my soon to be employer) adds ALOT of bloat to anything they release for the sake of making it **pretty**. The libraries and stuff are prolly only some 10% of the entire package, the rest being chm help files, sample code, etc etc etc **puke**. I have come to like and appreciate what linux is doing, but some things are still hard to do correctly in it. For example, dual mons. (ANYONE with dual mons and linux knows exactly what I'm talking about). VS is cake to use if you're provided with the sln files and all the libs you need to dl, which pretty much suffers the same problem in linux. Dependency hell blows badly. As far as code deprecation is concerned (namely the fopen "warning") I can only assume the purpose of that is to get devs to realize they won't be able to use those c-runtime functions for much longer. They are inherently unsafe by no fault of the OS, and soon I imagine the Windows OS will have a thick layer between the OS and any application and completely block stuff like "fopen" and raw socket stuff to ward off potentially malicious code.
Windows OS will have a thick layer between the OS and any application and completely block stuff like "fopen" and raw socket stuff to ward off potentially malicious code.
In the MSDN library it says:
"It should be noted that in this context, "deprecated" just means that a function's use is not recommended; it does not indicate that the function is scheduled to be removed from the CRT."
As far as code deprecation is concerned (namely the fopen "warning") I can only assume the purpose of that is to get devs to realize they won't be able to use those c-runtime functions for much longer. They are inherently unsafe by no fault of the OS
I have to disagree with that, fopen/fputs/fwrite is not inherently unsafe by itself. It's just the pointer handling that makes C/C++ unsafe, but that applies to any part of C/C++. I would say iostream is just as safe or unsafe as fopen/fclose.
I have to disagree with that, fopen/fputs/fwrite is not inherently unsafe by itself.
I would say that they are inherently unsafe in the same way a sharp knife is. Both are very useful tools, but if used wrong either can have very bad conquences.
Joined: 01 Jun 2005, 10:36 Location: The Netherlands
Quote:
C makes it easy to shoot yourself in the foot; C++ makes it harder, but when you do, it blows away your whole leg.
Quote:
If C gives you enough rope to hang yourself, then C++ gives you enough rope to bind and gag your neighborhood, rig the sails on a small ship, and still have enough rope to hang yourself from the yardarm.
Joined: 26 Aug 2004, 07:11 Location: Virginia Tech
I know that's what MSDN says, but I wouldn't be surprised if a future version of windows ran all applications in a sandbox and disallowed stuff like fopen ^_^. While fopen is not inherently unsafe, it can be more easily abused by manipulating pointers sent to it etc. The idea is to move all the low level pointer stuff to trusted code, and tell you that the compiler thinks using fopen isn't the best way of doing things.
I am using the free copy of Visual C++ 2005 off the Microsoft website. RTS finally compiles, but it is asking for LIBC.lib. I read greenail's instructions, but I don't understand them. Would you please give this C++ newbie a little more help? Thanks. EDIT: If anyone wants a copy of boost compiled for VS8.0 I'd be happy to send it. I just don't have any web space.
I too have this LIBC.lib error. what did I forgot to do? forgive my noobz question. Any solution?
At soem point I was told that LIBC couldnt be sued because another library was itnerfering, I fixed it but it was a while ago and I've nto ahd that error in a long while
Compiler does not allow const_cast to down cast under /clr:oldSyntax Prior to Visual C++ 2005 the Visual C++ compiler allowed the const_cast Operator to down cast when compiling source code that uses Managed Extensions for C++ syntax. Performing a down cast with const_cast now results in Compiler Error C2440. To resolve, use the correct cast operator (for more information, see Casting Operators). This change was made for conformance reasons.
VS2005 doesn't allow down casting of const char...
Compiler does not allow const_cast to down cast under /clr:oldSyntax Prior to Visual C++ 2005 the Visual C++ compiler allowed the const_cast Operator to down cast when compiling source code that uses Managed Extensions for C++ syntax. Performing a down cast with const_cast now results in Compiler Error C2440. To resolve, use the correct cast operator (for more information, see Casting Operators). This change was made for conformance reasons.
VS2005 doesn't allow down casting of const char...
Nm, I solved it by using old version of boost (1.33) instead of latest stable (1.33_1) .. for the reasons beyong my comprehension this solved the problem..
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
Home
Download
Login
Register
FAQ
Search
