VS 2022 is not C friendly
-
jmaida wrote:
#include <glfw glfw3.h=""> fails not matter how I reference that the directory it is located in. D:\code\glfw3.3.8\include NOT A TYPO ANYWHERE
Apart from the fact that the include statement is totally incorrect. And again, that is nothing to do with Visual Studio, but one for the compiler. Well, strictly speaking, it's the preprocessor, but we'll let that pass.
-
You can link to static lib from a static lib in VS in C. I've done it, but I'm not gonna tell you how. Why? Because of your attitude. Life's too short. Keep on Googling.
Jeremy Falcon
-
David O'Neil wrote:
If you selected 'static library project' it is set to CREATE a static library
Home dude isn't here to learn. He's here to rant.
Jeremy Falcon
-
A static library cannot use another static library. What exactly do you mean? Honestly VS is perfectly fine, it's, as almost always, the users... :laugh:
-
Try again, you can still write a static lib in C in VS2022. You don't need to use pragmas either. While I'm not a fan of VS these days as it's too bloated, at least be fair and do the research before saying something sucks because it can't do something - when it can. We're supposed to be mature professionals. Supposed to be...
Jeremy Falcon
-
Python?!? Hell no! But there are much better tools out there than VS, specially if one is interested in programming just in C, without any of those C++isms...
-
Code Blocks is more straight forward
"A little time, a little trouble, your better day" Badfinger
If you want to do JUST C, try taking a look at Pelle's C. None of the C++ stuff, just by default, compliant with the latest C standard. Freeware, but not Open Source. But certainly the price tag fits...
-
Well, if you're used to Turbo C, try Embarcadero C++Builder, though I personally don't like the price tags anymore... That's why I switched for my daily programming work to FreePascal+Lazarus instead of Delphi more than a decade ago.
-
doing so as we espeak. BTW reading your article too.
"A little time, a little trouble, your better day" Badfinger
Here is a suggestion. Stop ranting about something you are having problems with. Go to https://www.codeproject.com/Questions/ask.aspx[^] and post the full details, so people can try to help you. And make sure you check what you post, so you can fix any typos, and ensure that all code snippets are surrounded by the appropriate <pre> tags so it is readable, like:
#include "somefile.h"
int main()
{
printf("Hello, World!");return 0;}
Tags used in the above case are: <pre lang="C++"> and </pre>
-
#include is what editor to lounge did. Not me #include is what was supposed to be sent. Something was awry.
"A little time, a little trouble, your better day" Badfinger
-
Python?!? Hell no! But there are much better tools out there than VS, specially if one is interested in programming just in C, without any of those C++isms...
-
Ralf Quint wrote:
But there are much better tools out there than VS
Bash scripts and make?
No bash, and no make, if one can avoid it. But for C programming, as per original post, there's for example Pelle's C, which is not only a fraction of the size of VS, but also Freeware. Commercially, then there is Embarcadero's Delphi/C++Builder/RAD Studio, and FreePascal/Lazarus are an Open Source Object Pascal option. All of those are smaller and easier to use than VS. But it seems that some people just stick to VS because of their masochistic tendencies, just like a lot of macOS users think they just have to punish themselves by using XCode...
-
I do not like to argue all day long. I am looking for helpful input. I have received it and I have taking everyone's advice, but I still cannot get VS to behave. Frustrating. OK. You can call it ranting. So what. I am an extremely experienced C programmer (I have also written code in C, Fortran, Cobol, Algol, PL/I ...) as well. Writing C code since K&R first publication, so feel qualified to complain. I am retired now and doing some experimenting using GLFW's VS libraries to facilitate porting a large body of work to VS for programmers at a former employer. I will calmly say VS is not a user/programmer friendly application. I have used it on and off since it first came out and it keeps getting worse. But I will solve this problem.
"A little time, a little trouble, your better day" Badfinger
jmaida wrote:
I will calmly say VS is not a user/programmer friendly application.
I started with hand written scripts. Then I think I went to Borland IDE. Then the first Microsoft IDE (not called VS) Finally then I go to make files, then maven, then back to VS and then back to make/maven, then back to VS (going back and forth several times.) Eclipse is in there some where but I gave up on that right away (twice actually.) And at least one custom built build system in there as well. None of them were user friendly. Might note of course that I have written many applications also and the universal truth is that power and simplicity are not possible in the same application. The command line tools cat/type are pretty dang easy to use. The editor that I have been using for 20 years (not part of an IDE) still manages to make me jump through hoops every time I have to install it on new box just to get it to work the way I want.
jmaida wrote:
But I will solve this problem.
Having fought with VS many times, all I can say is that there is a way to solve the problem you described.
-
jmaida wrote:
I will calmly say VS is not a user/programmer friendly application.
I started with hand written scripts. Then I think I went to Borland IDE. Then the first Microsoft IDE (not called VS) Finally then I go to make files, then maven, then back to VS and then back to make/maven, then back to VS (going back and forth several times.) Eclipse is in there some where but I gave up on that right away (twice actually.) And at least one custom built build system in there as well. None of them were user friendly. Might note of course that I have written many applications also and the universal truth is that power and simplicity are not possible in the same application. The command line tools cat/type are pretty dang easy to use. The editor that I have been using for 20 years (not part of an IDE) still manages to make me jump through hoops every time I have to install it on new box just to get it to work the way I want.
jmaida wrote:
But I will solve this problem.
Having fought with VS many times, all I can say is that there is a way to solve the problem you described.
All that you have said, is very familiar to me, Eclipse, VS, Borland, Codeblocks, Geany (weird little editor/app) and of course Linux stuff with it's own IDE baggage (I have forgotten must of it and it's weird vi editor) For windows environments, I settled on Codeblocks because it stayed relatively the same as far as the interfacing, program settings, etc. Their editor is quite good, one of the best, I think. They add some new plugins now and then, but not too pushy. But if someones puts it down, I let go as not their cup of tea. We all have our fancies. I did business with a German company years ago and their programmers and I had no problems working together other some German/English language issues, but we all had similar likes and dislikes. Thanks for encouragement. VS can be frustratingly fluid.
"A little time, a little trouble, your better day" Badfinger
-
Here is a suggestion. Stop ranting about something you are having problems with. Go to https://www.codeproject.com/Questions/ask.aspx[^] and post the full details, so people can try to help you. And make sure you check what you post, so you can fix any typos, and ensure that all code snippets are surrounded by the appropriate <pre> tags so it is readable, like:
#include "somefile.h"
int main()
{
printf("Hello, World!");return 0;}
Tags used in the above case are: <pre lang="C++"> and </pre>
Thanks Richard, When I can compile more specific details I will do so. I have some weird problem where VS compiles the same simple C file (single file) with two different results. It's a test file from vendor's web site that uses their libraries. Very good suggestion. A helpful one that I should have used right off. I have even suggested in the past to others. Oh well.
"A little time, a little trouble, your better day" Badfinger
-
'Xactly. Me too. Kids these days expect everything to be handed to them. I also learned on OpenVMS, which has a debugger, but it's practically unusable.
unusable? I'm offended. :) Last week I was debugging some ancient FORTRAN, and it did just fine. Seriously though, it takes a while for the muscle memory to kick in to remember the keypad commands.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I will. Thank you. I blame VS because 1. Have 2 copies of exactly the same C file. 2. Put them into VS "exactly" the same way (here is where the rub is, because VS makes that more complicated than it should be as "exactly" is not what has happened) 3. one works fine, the other does not. 4. Did a difference on .project files. Not "exactly" the same. That is what I am trying to resolve. If it is user error then shame on VS for making it easy to do.
"A little time, a little trouble, your better day" Badfinger
-
unusable? I'm offended. :) Last week I was debugging some ancient FORTRAN, and it did just fine. Seriously though, it takes a while for the muscle memory to kick in to remember the keypad commands.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
You are obviously hoopier frood than I. The main issue I had was that I couldn't get the debugger to display the source lines involves. (DEC C) "User error" I'm sure.
-
Thanks Richard, When I can compile more specific details I will do so. I have some weird problem where VS compiles the same simple C file (single file) with two different results. It's a test file from vendor's web site that uses their libraries. Very good suggestion. A helpful one that I should have used right off. I have even suggested in the past to others. Oh well.
"A little time, a little trouble, your better day" Badfinger