As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I know it's a standar c library, but I don't understand why c doesn't have a free library, not one that is lgpl. Is there any such library and if not, than that means every company/particular developer has to buy even the most basic libraries to develop commercial apps ?
every company/particular developer has to buy even the most basic libraries to develop commercial apps ?
Well, they have to buy (or get for free) the compiler anyway, and libc comes with it.
Also, writing an universal C library is impossible, since exit(), setjmp(), etc. depend on the particular compiler and platform.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
What are the specific operations a language runtime does that an operating system does not? How is a language runtime different from a middleware?
This depends on the operating system and the runtime. libc is a good example of a language runtime and the linked article on Wikipedia gives a good overview of what it does. Generally the goal of a language runtime is to provide implementations of standard basic functionality which is likely to be implemented differently between the operating systems the language supports, or functionality which is extremely common, but not provided by the operating system.
Middleware is a very general concept but it simply refers to software placed between two systems as an abstraction layer. You could consider a language runtime as a form of middleware in some contexts.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I need to write client and server applications for MS-DOS using C language.
I don't want to start from scratch and implement sockets.
Can you advice me library in which socket functionality is implemented and for which exist good manuals and examples.
I already tried mTCP library: I got source files from it, added sources from example file and tried to Compile in Turbo C, but it raises a lot of errors it will be very hard task for me to cope with them.
Try libnet. According to it's web page (http://libnet.sourceforge.net/) it supports DOS systems (djgpp compiler), though I personally haven't tried it on DOS.
There is also WATTCP: http://www.erickengelke.com/wattcp/
Have you tried that?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I want to create a tool which analyzes a C program for critical sections during the compilation phase. I am looking for the right algorithm which would let me do this. It can be at any phase of the compiler.
You may be interested in this article “Static analysis of run-time errors in embedded real-time parallel C programs”.
The Frama-C plug-in mthread was developed simultaneously and independently. It works on comparable principles.
Each of the above two tools is man-years of work over an existing base that already represents at least ten man-years of work. As some have already commented, if you want to do anything significant and useful for the kind of moderately large program that you cannot just read to convince yourself that it is correct, you are going to have a lot of work.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I apologize for my bad English.
Why does the C89 library not contain functions to create/delete/rename/remove a directory? Or maybe I didn't find that? I see functions for some file operations only, but not for directories.
Thank you
Best Regards
Otherwise, <dirent.h> header file is now pseudo-standard: both MinGW and GCC have it. So, you can handle directories on a conventional personnal computer, without too much trouble.
Traditionally (and C89 is tradition) the directory structure is seen as part of the operating system, and at the time (1989) there were still OS arround that had incompatible concepts for that.
Nowadays, there would perhaps be enough common ground to integrate such a thing in C, as it is e.g now done for threading in C11, but I am not aware of an initiative to do so.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
see ,
still yet i have seen that most of the embedded application are written in c.
Most of the libraries are written in c.
Device-driver are written in c.
So i want to ask you is there any logical reason behind this?
(My apologies if this post sounds silly/stupid. I thought I'd ask here. Ignoring these core bits never made anyone a better programmer.)
There are many reasons, including but not limited to:
It has access to many low level functions not accessible from many other languages.
It has existed for many many years and has lots of developers that are familiar with it.
If written well it's extremely efficient.
It gives almost complete control over memory etc.
It's very portable, largely due to the myriad of compilers written for it.
Because of Dennis Ritchie. C is easily the most portable language.