News for hackers. Stuff that matters.
Re:Building C Projects by gnuvince on Wednesday November 05, 2014 @09:56PM (#8565570)
> C is a compiled language[...]

Not off to a great start :/

Re:Building C Projects by angersock on Wednesday November 05, 2014 @10:14PM (#8565627)
Eh?

Um...that's true?

Re:Building C Projects by brandonbloom on Wednesday November 05, 2014 @10:22PM (#8565650)
Compiled vs interpreted is not a property of the language. It's a (vague) property of a particular implementation.
Re:Building C Projects by sjolsen on Wednesday November 05, 2014 @10:36PM (#8565682)
> Compiled vs interpreted is not a property of the compiler.

I assume you meant "language." You're of course correct, but if ever there were a language that deserved to be called "compiled," C is it. It truly was designed to be compiled, and who in their right mind would bother interpreting it?

And before you ask, no, people who debug C are rarely in their right minds. :)

Re:Building C Projects by zik on Wednesday November 05, 2014 @11:03PM (#8565740)
> ...who in their right mind would bother interpreting it?

Um... me?

https://code.google.com/p/picoc/

Re:Building C Projects by e12e on Thursday November 06, 2014 @03:31AM (#8566235)
That's really an interpreter (as opposed to using a bytecode vm or some such)? How does it deal with memory allocation, alignment etc? And (I don't have a proper dev setup on hand) -- the obvious question -- can it run itself, in itself in itself? (And itself in tcc in itself?) ;-)
Re:Building C Projects by zik on Thursday November 06, 2014 @05:45PM (#8570287)
It's a real interpreter. It runs directly from the source code - it doesn't even store a parse tree or bytecode. Memory allocation and alignment is done in the standard C ways. It's designed as a scripting variant of C so it doesn't implement 100% of the C standard (eg. bitfields), so no it's not self-hosting.
Re:Building C Projects by e12e on Friday November 07, 2014 @12:50AM (#8571362)
Fascinating, I'll have to look at it more closely when I've got a usable command line available. I would not have thought it was feasible for a useful subset of C -- but then I tend to forget that it is a rather simple language at heart (eg: after running the pre-prosessor).
Re:Building C Projects by angersock on Thursday November 06, 2014 @01:06PM (#8568566)
Do you support GOTOs?

#ifdefs?

aligment #pragmas?

#includes?

extern?

If you don't--which is integral to how C works--you've created a cool C-like language, but not C.

C is quite nearly just a high-level assembler with syntax sugar.

Re:Building C Projects by brandonbloom on Wednesday November 05, 2014 @11:37PM (#8565805)
Yes, of course, I've fixed my post. Thanks.

> if ever there were a language that deserved to be called "compiled," C is it.

I was only clarifying the other guy's comment, but I do appreciate the desire to be careful with the meaning of technical terms, lest they get diluted and become less useful.

> It truly was designed to be compiled, and who in their right mind would bother interpreting it?

Lots of people can (and do!) interpret C, or some subset, superset, or abstraction of C, for a great many purposes. Consider debuggers, IDEs, formal verification systems, build systems, security tools, etc.

Re:Building C Projects by orbifold on Thursday November 06, 2014 @02:13AM (#8566085)
Physicists at CERN :), their analysis framework ROOT is bundled with a C/C++ interpreter. I had only occasion to use it once, but it was a fairly pleasant experience.
Re:Building C Projects by klibertp on Thursday November 06, 2014 @04:05AM (#8566304)
> and who in their right mind would bother interpreting it?

https://www.softintegration.com/

> It truly was designed to be compiled

I'm not sure - what qualities of a language make it designed for compilation?

Re:Building C Projects by simias on Thursday November 06, 2014 @09:29AM (#8567109)
> I'm not sure - what qualities of a language make it designed for compilation?

I'd say no high level abstractions, no need for a runtime keeping track of what you're doing (garbage collector, bound checks etc...)

The standard also describes a bunch of undefined/undetermined behaviours to let the compiler generate machine code as efficient as possible and without the need for a runtime (or as small a runtime as possible).

None of those things forbid an interpreted implementation but it makes less sense to leave those gotchas into the language if you don't have to talk to the CPU directly, it makes more sense to let the interpreter take care of the architecture-dependent details.

But pedants are going to be pedants.

Re:Building C Projects by sjolsen on Thursday November 06, 2014 @10:56AM (#8567567)
> what qualities of a language make it designed for compilation?

That a language that compiled to good machine code was one of the main goals of the people who designed it. I was making a historical statement, not a qualitative one.

Re:Building C Projects by chrisseaton on Thursday November 06, 2014 @08:34AM (#8566895)
> who in their right mind would bother interpreting it?

In some cases interpreting C can be faster and more convenient: http://www.chrisseaton.com/rubytruffle/cext/.

Re:Building C Projects by WallWextra on Thursday November 06, 2014 @01:47AM (#8566049)
Meanwhile, in reality, C is a compiled language.
Re:Building C Projects by lsiebert on Thursday November 06, 2014 @02:34AM (#8566123)
People tend to compile their C code. It's probably more accurate to speak of tendencies in how it's implemented and used then to assign attributes to the language.
Re:Building C Projects by WallWextra on Thursday November 06, 2014 @03:11AM (#8566192)
No, it's accurate to describe reality rather than hypotheticals.
Re:Building C Projects by ghshephard on Thursday November 06, 2014 @04:38AM (#8566370)
And the reality is that languages are not compiled or interpreted, but there are implementation of language compilers or interpreters. The C language isn't "compiled", but there are some implementations of C compilers, and some implementations of C interpreters.

Another good example, is an old language, "BASIC", which a lot of people used the interpreted version, but, as early as 1987, I used a BASIC compiler which provided as much as a 100x increase in performance over the common interpreter that came with my system.

Python is another great example - lots of Python interpreters out there, but Cython lets you compile your python code to machine code.

Re:Building C Projects by vinceguidry on Thursday November 06, 2014 @10:18AM (#8567344)
So, what you're saying is that C is (usually) compiled?
Re:Building C Projects by dap on Thursday November 06, 2014 @09:48AM (#8567183)
FWIW, from the post:

> A disclaimer: this post focuses on how things typically work on modern consumer operating systems (especially Linux and Windows), rather than trying to cover all possible obscure systems. C doesn't have to work like this. It just normally does in practice.

Re:Building C Projects by cbd1984 on Thursday November 06, 2014 @12:12AM (#8565881)
And then there's the rest of the world:

Python: Interpreted language, right? Then what are all those .pyc files doing? You can say it's compiled into an interpreted form, but then JVM bytecode comes along, which is interpreted right up until you find an implementation that JITs. Or is it only compiled if you save the compiled form to disk, like you do with gcj?

Scheme: An interpreted language in Guile, a compiled language in Stalin?