Welcome to the Lounge

Re: What did one wall say to the other?

22-Jan-23 10:53

Meet me at the corner.
Booo

"A little time, a little trouble, your better day"
Badfinger

Slacker00722-Jan-23 11:07

Slacker007

22-Jan-23 11:07

Are you sure they did not say Visual Studio sucks?

Re: What did one wall say to the other?

jmaida22-Jan-23 11:35

22-Jan-23 11:35

After they meet

"A little time, a little trouble, your better day"
Badfinger

worldle 366 1/6

jmaida22-Jan-23 10:27

22-Jan-23 10:27

#Worldle #366 1/6 (100%)
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
easy one - and was just discussing this at lunch today.

"A little time, a little trouble, your better day"
Badfinger

ISS modules

Calin Negru22-Jan-23 19:40

Calin Negru

22-Jan-23 19:40

I was always puzzled how hatches on space stations stay tight sealed. Today I had a revelation. A space station is like a submarine just the other way around. On a submarine the exit hatch opens towards the outside. When closed the water pressure pushes the hatch against the door step frame because the hatch is on the outside. On ISS the hatches are on the inside. The ISS modules are pressurized so the pressure from the inside pushes the hatch against the door step creating a tight seal. The only thing that still remains a mystery in my mind is how two hatches bind to each other.

OriginalGriff22-Jan-23 10:00

OriginalGriff

22-Jan-23 10:00

Have a look here: SPACE SHUTTLE ORBITAL DOCKING SYSTEM[^]
And for more details on the docking hatch itself, see here: ALL IN for PROJECT EGRESS - This Old Tony[^] and the main project "Project Egress" Build | National Air and Space Museum[^]

"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

Calin Negru23-Jan-23 4:16

Calin Negru

23-Jan-23 4:16

Thanks

jmaida22-Jan-23 10:13

22-Jan-23 10:13

For a more generalized description of docking/berthing/mating this article is very good.

Docking and berthing of spacecraft - Wikipedia[^]

"A little time, a little trouble, your better day"
Badfinger

Slacker00722-Jan-23 11:06

Slacker007

22-Jan-23 11:06

passenger jet liners are similar. their doors and panels are designed to pressurize outward; actually most jets are that way. Pressurized water can get inside the plane when it is on the ground (i.e. de-icing, etc.). The cracks in the door and panel seals don't fully close until the plane is at altitude and it can pressurize.

VS 2022 is not C friendly

OriginalGriff22-Jan-23 11:31

OriginalGriff

22-Jan-23 11:31

And it's designed that way so passengers can't open the door in flight.

jmaida21-Jan-23 17:33

21-Jan-23 17:33

I have been trying to create a static library (in C) that uses another published static library.
No where does VS do I have link options to include that library.
VS SUCKS

"A little time, a little trouble, your better day"
Badfinger

Shao Voon Wong21-Jan-23 17:47

Shao Voon Wong

21-Jan-23 17:47

You can try to link the static lib by specifying this pragma statement in any c source file.

#pragma comment(lib, "c:\\your_folder\\your_lib.lib")

Shao Voon Wong21-Jan-23 18:01

Shao Voon Wong

21-Jan-23 18:01

The reason the VC++ static library project does not have the linkage option is that the static library does not have to link to any library, the source code file only needs to include the headers file to compile correctly.

The executable project that uses your C static library must link with both static libs in the link options.

modified 22-Jan-23 0:13am.

jmaida21-Jan-23 18:09

21-Jan-23 18:09

Thanks. Pragma's seem to the answer to all the weird VS behavior I have encountered such as fopen vs fopen_s etc.

"A little time, a little trouble, your better day"
Badfinger

Richard MacCutchan21-Jan-23 22:10

Richard MacCutchan

21-Jan-23 22:10

jmaida wrote:
weird VS behavior I have encountered such as fopen vs fopen_s etc.

Again, that has nothing to do with Visual Studio, but only the code that you are writing.

Slacker00721-Jan-23 22:57

Slacker007

21-Jan-23 22:57

A lot of members here at Code Project love to hate on Visual Studio for no intelligent reason at all.

"I got into a car crash this morning, I hate Visual Studio."
"I stubbed my toe getting out of bed this morning, Visual Studio sucks!!"

"I don't know what I am doing, it's Visual Studio's fault!"

the list literally goes on forever...

Sigh | :sigh:

modified 22-Jan-23 5:07am.

jschell22-Jan-23 9:14

jschell

22-Jan-23 9:14

Slacker007 wrote:
A lot of members here at Code Project love to hate on Visual Studio for no intelligent reason at all.

But they express undying love for some other bit of technology? Which bit is that exactly?

Our Forgotten Astronomy | Object Oriented Programming with C++ | Wordle solver

David O'Neil22-Jan-23 10:47

David O'Neil

22-Jan-23 10:47

Python.

Ralf Quint23-Jan-23 19:31

Ralf Quint

23-Jan-23 19:31

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...

jschell24-Jan-23 9:44

jschell

24-Jan-23 9:44

Ralf Quint wrote:
But there are much better tools out there than VS

Bash scripts and make?

Ralf Quint24-Jan-23 9:49

Ralf Quint

24-Jan-23 9:49

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...

jmaida22-Jan-23 9:31

22-Jan-23 9:31

I TOTALLY disagree. The code I am working with is just a simple basic C libary. In VS I chose static library, etc. The problem is VS is way too complicated, trying to do to many things for too many types of language applications. I have used VS off and on for years so I know what I am talking about. I came back to it because of potential conversion of a large graphics application that will be "potentially" ported to it. I am quickly changing my mind as to whether it is worth it or not. The application is mostly window's agnostic.

"A little time, a little trouble, your better day"
Badfinger

Richard MacCutchan22-Jan-23 22:41

Richard MacCutchan

22-Jan-23 22:41

jmaida wrote:
The problem is VS is way too complicated

Well, I totally disagree with you on that. And I have been using it, or its predecessors, for almost thirty years. I have created complete applications, and static and dynamic libraries, using C, C++, C# and even VB.NET, so I also know what I am talking about.