c/pascal compiler differences

[Skybuck Flying]

Hi,

I think I understand now a bit better what the difference is between a c
compiler and a pascal compiler.

For example:

When compiling source code with a pascal compiler. The pascal compiler will
simply stop when it is missing an implementation for a procedure or
whatever.

The c compiler however will simply continue compiling even if the
implementation for the headers/prototypes are missing.

The c linker will then report a big list of link errors.

Both methods have benefits and drawbacks. The pascal compiler is more
simple... it allows one to simply proceed from error to error until it
completely compiles and links.

The drawback of the c compiler might be the suspended error reporting...
it's a bit wacky... since one can not jump to the location where the stuff
is missing ?

or maybe one can... it's a bit wacky...

Though I can clearly see a benefit for a c compiler since it simply compiles
even though the implementation is completely missing.

One could later even make different implementations and simple re-use the
already compiled stuff and link against it.

So one can end up linking different kind of stuff against the same compiled
C file.

I think this is correct though I never really tried it.

Are there any good examples where this C/link freedom is used ?

Does a pascal compiler have the same link freedom ? ( meaning prototype
available but implementation missing )

I think not... ?

Bye,
Skybuck.

[Bruce Roberts]

"Nicolai Hansen" <ni*@aub.dk> wrote in message
news:d9******** *************** **@posting.goog le.com...

This will compile, this will generate an object file, but this will
not generate an executable. It will say something like "LINKER ERROR:
unsatisfied external "void MyMethod()" in file test.c".
At a later time you can then make a file test2.c

If you take a look at a project directory that contains a built project you
will note that each unit has a .dcu file. This is the "object" file for the
unit. Using the command line compiler one can compile a discreet Delphi
unit.

[Bruce Roberts]

"Skybuck Flying" <no****@hotmail .com> wrote in message
news:cg******** **@news3.tilbu1 .nb.home.nl...

The whole point ofcourse is that in C one doesn't need any link directives

?

And what, pray tell, is the reason for a MAKE file? At some point the linker
has to be told what units to link together. It doesn't matter if one is
writing C or Delphi. Or have you found a compiler that somehow divines a
programmer's intentions regarding separately compiled units?

[Skybuck Flying]

"Bruce Roberts" <be*@bounceitat tcanada.xnet> wrote in message
news:c1******** *******@news20. bellglobal.com. ..

"Skybuck Flying" <no****@hotmail .com> wrote in message
news:cg******** **@news3.tilbu1 .nb.home.nl...

The whole point ofcourse is that in C one doesn't need any link

directives ?

And what, pray tell, is the reason for a MAKE file? At some point the linker has to be told what units to link together. It doesn't matter if one is
writing C or Delphi. Or have you found a compiler that somehow divines a
programmer's intentions regarding separately compiled units?

Ok I was just screwing around with D8 libraries naturally D8 is a piece a
shit and nothing is working...

But now that I tried using a library in delphi I can see how it might work
in D7 :)

procedure blabla; external 'somefricking.d ll';
begin

blabla;

end;

This might actually compile and build in delphi

actually I am pretty sure lol..

But this simple because this is just a dll...

But euhmm with the link directive it might work as well...

But wtf are .obj files ? :)

Does that include C generated files ?

Or delphi generated DCU's ?

Can I link a DCU file as well ? just like that... with the external stuff ?

Seeya.

[Skybuck Flying]

"Bruce Roberts" <be*@bounceitat tcanada.xnet> wrote in message
news:rZ******** *******@news20. bellglobal.com. ..

"Nicolai Hansen" <ni*@aub.dk> wrote in message
news:d9******** *************** **@posting.goog le.com...

This will compile, this will generate an object file, but this will
not generate an executable. It will say something like "LINKER ERROR:
unsatisfied external "void MyMethod()" in file test.c".
At a later time you can then make a file test2.c
If you take a look at a project directory that contains a built project

you will note that each unit has a .dcu file. This is the "object" file for the unit. Using the command line compiler one can compile a discreet Delphi
unit.

Can delphi do this ?

Some fricking unit 1

function bleh : string;
begin
result := 'bleh';
end;
some fricking main pascal/delphi program

{$LINK 'some fricking unit1.dcu'}

function bleh; external; // ?

begin

writeln( bleh )
readln;
end;

???? :)

Bye,
Skybuck.

[Skybuck Flying]

"Bruce Roberts" <be*@bounceitat tcanada.xnet> wrote in message
news:rZ******** *******@news20. bellglobal.com. ..

"Nicolai Hansen" <ni*@aub.dk> wrote in message
news:d9******** *************** **@posting.goog le.com...

This will compile, this will generate an object file, but this will
not generate an executable. It will say something like "LINKER ERROR:
unsatisfied external "void MyMethod()" in file test.c".
At a later time you can then make a file test2.c
If you take a look at a project directory that contains a built project

you will note that each unit has a .dcu file. This is the "object" file for the unit. Using the command line compiler one can compile a discreet Delphi
unit.

Wait don't tell me one has to use USES for that ?

DOH

Fuck the link directive..

Why can't I simply use this:

Uses
SomeFrickingObj ect.OBJ :) hehehehe

[Skybuck Flying]

"Bruce Roberts" <be*@bounceitat tcanada.xnet> wrote in message
news:rZ******** *******@news20. bellglobal.com. ..

"Nicolai Hansen" <ni*@aub.dk> wrote in message
news:d9******** *************** **@posting.goog le.com...

This will compile, this will generate an object file, but this will
not generate an executable. It will say something like "LINKER ERROR:
unsatisfied external "void MyMethod()" in file test.c".
At a later time you can then make a file test2.c
If you take a look at a project directory that contains a built project

you will note that each unit has a .dcu file. This is the "object" file for the unit. Using the command line compiler one can compile a discreet Delphi
unit.

Really man the link directive is crazy...

All these years I have been programming high up in clouds lol.. hehehehehe

YESSSsssss

Never having to worry or know what it is that delphi does when I press the
build button...

And now suddenly I am confronted with a link directive !

FUCK :)

Shame on you borland for not abstracting that :D LOLOLOLOLOLOLO

[CBFalconer]

Bruce Roberts wrote:

"Nicolai Hansen" <ni*@aub.dk> wrote in message

This will compile, this will generate an object file, but this
will not generate an executable. It will say something like
"LINKER ERROR: unsatisfied external "void MyMethod()" in file
test.c". At a later time you can then make a file test2.c

If you take a look at a project directory that contains a built
project you will note that each unit has a .dcu file. This is
the "object" file for the unit. Using the command line compiler
one can compile a discreet Delphi unit.

And what has this got to do with comp.lang.c? Please restrict the
cross-posting of things that are off-topic on some groups. All
you have to do is religiously set follow-ups, as I have done.

--
Chuck F (cb********@yah oo.com) (cb********@wor ldnet.att.net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home .att.net> USE worldnet address!

[RCollins]

Skybuck Flying wrote:

"Bruce Roberts" <be*@bounceitat tcanada.xnet> wrote in message
news:c1******** *******@news20. bellglobal.com. ..

"Skybuck Flying" <no****@hotmail .com> wrote in message
news:cg****** ****@news3.tilb u1.nb.home.nl.. .

The whole point ofcourse is that in C one doesn't need any link

directives

?

And what, pray tell, is the reason for a MAKE file? At some point the

linker

has to be told what units to link together. It doesn't matter if one is
writing C or Delphi. Or have you found a compiler that somehow divines a
programmer' s intentions regarding separately compiled units?

Ok I was just screwing around with D8 libraries naturally D8 is a piece a
shit and nothing is working...

But now that I tried using a library in delphi I can see how it might work
in D7 :)

procedure blabla; external 'somefricking.d ll';
begin

blabla;

end;

This might actually compile and build in delphi

actually I am pretty sure lol..

But this simple because this is just a dll...

But euhmm with the link directive it might work as well...

But wtf are .obj files ? :)

Does that include C generated files ?

Or delphi generated DCU's ?

Can I link a DCU file as well ? just like that... with the external stuff ?

Seeya.

None of this stuff has anything to do with the C language. It is all
specific to the brand of compiler you are using (Microsoft or Borland).
"obj" files are compiled (but not linked) created by Microsoft
compilers; "dcu" files are compiled (but not linked) created by Borland
Delphi compilers.

You would get more usefull info by checking in a Microsoft and/or
Borland newsgroup.

--
Ron Collins
Air Defense/RTSC/BCS

[Giorgos Keramidas]

"Skybuck Flying" <no****@hotmail .com> writes:

Why can't I simply use this:

Uses
SomeFrickingObj ect.OBJ :) hehehehe

Ask in a Delphi newsgroup but please keep comp.lang.c out of this.
The intricacies of Delphi are totally unrelated to C.

[-- Followups properly redirected --]