«

Hello, my english is very poor, excuse me. I want that someone explains
several things.
Ok,

Windows, as well as other modern operating systems, gives a set of
functions called API. The programmer can access to the functionalities
of the system by them. Is it right? The functions are grouped, for
example kernel and user. Now, in a compiler as gcc what does
libkernel32.a represent? The dll are written in C and then why do we
use libkernel32.a and not kernel.dll?
What are files lib*.a? Thank you very much!

Bye

dvddum

dvdsum wrote:
> Hello, my english is very poor, excuse me. I want that someone explains
> several things.
> Ok,
>
> Windows, as well as other modern operating systems, gives a set of
> functions called API. The programmer can access to the functionalities
> of the system by them. Is it right? The functions are grouped, for
> example kernel and user. Now, in a compiler as gcc what does
> libkernel32.a represent? The dll are written in C and then why do we
> use libkernel32.a and not kernel.dll?
> What are files lib*.a? Thank you very much!

This group tries to confine itself to the standard C language. Posting
is a more specific group like comp.os.ms-windows.programmer etc., will
yield you a better and more accurate response. To answer you just this
once, the *.a files are 'import' files which enable proper compilation
and runtime loading of the corresponding *.dll.

dvdsum a écrit :
> Hello, my english is very poor, excuse me. I want that someone explains
> several things.
> Ok,
>
> Windows, as well as other modern operating systems, gives a set of
> functions called API. The programmer can access to the functionalities
> of the system by them. Is it right? The functions are grouped, for
> example kernel and user. Now, in a compiler as gcc what does
> libkernel32.a represent? The dll are written in C and then why do we
> use libkernel32.a and not kernel.dll?
> What are files lib*.a? Thank you very much!
>
> Bye
>
> dvddum
>

Compiled functions are grouped in files called "libraries". Those files
contain several compiled functions that perform various functions like
drawing a line, opening a file, making coffee, etc.

Libraries are normally called file.lib under windows, or libfile.a under
Unix. Since gcc comes from Unix, it names its libraries .a instead of
..lib.

Libraries can come in two "flavors". Normal "static" libraries, that
contain the code of the functions, and "import" libraries that are
just stubs that tell the dynamic linker/loader where those functions
are actually defined. When you use a dll (or a shared object using Unix
naming conventions) your libraries allows your executable to be
associated to a dynamic library (a .dll under windows a .so under
Unix). In your example libkernel32.a just associates some of
the functions that you use in your program with kernel32.dll.

Under windows you can use the dll directly (without linking to it) by
using the LoadLibrary API. Under Unix you use dlopen() or similar
functions. Note that you must link the dll that contains the
LoadLibrary API STATICALLY, you can't load kernel32.dll dynamically
since it containes the LoadLibrary API. In the same manner
it doesn't make sense to load the library that contains dlopen()
using dlopen()

jacob navia wrote:

<snip>

> associated to a dynamic library (a .dll under windows a .so under
> Unix). In your example libkernel32.a just associates some of
> the functions that you use in your program with kernel32.dll.

<snip>

Please redirect off topic questions to an appropriate place where your
errors will be corrected. If you want to know what the error is in the
above then *you* will have to ask in an appropriate group, I'll just say
that I know from personal experience that it is wrong in general
although had you been more specific it could have been correct.
--
Flash Gordon

In article <>,
Flash Gordon <> wrote:
>jacob navia wrote:
>
><snip>
>
>> associated to a dynamic library (a .dll under windows a .so under
>> Unix). In your example libkernel32.a just associates some of
>> the functions that you use in your program with kernel32.dll.
>
><snip>
>
>Please redirect off topic questions to an appropriate place where your
>errors will be corrected. If you want to know what the error is in the
>above then *you* will have to ask in an appropriate group, I'll just say
>that I know from personal experience that it is wrong in general
>although had you been more specific it could have been correct.

You're the sort who would tell someone that the phrase "The sun rises in
the East" is incorrect/worthless/immoral/fattening because of the
possibility that there might exists planets/worlds in which it doesn't
hold.

Technically right, I suppose, but, obviously, from the POV of any sane
person, utter BS.

[Just debunking some trollschildt]

Kenny McCormack said:

<snip>

> You're the sort who would tell someone that the phrase "The sun rises in
> the East" is incorrect/worthless/immoral/fattening because of the
> possibility that there might exists planets/worlds in which it doesn't
> hold.

It's incorrect for Venus, for example.

> Technically right, I suppose, but, obviously, from the POV of any sane
> person, utter BS.

So astronomers are not sane. How interesting.

--
Richard Heathfield
"Usenet is a strange place" - dmr 29/7/1999
http://www.cpax.org.uk
email: normal service will be restored as soon as possible. Please do not
adjust your email clients.

Richard Heathfield wrote:
> [Just debunking some trollschildt]
>
> Kenny McCormack said:
>
> <snip>
>
>> You're the sort who would tell someone that the phrase "The sun rises in
>> the East" is incorrect/worthless/immoral/fattening because of the
>> possibility that there might exists planets/worlds in which it doesn't
>> hold.
>
> It's incorrect for Venus, for example.

Indeed.

As it happens, on my post I had in mind a specific implementation that
comes from a large company and it used for mayor implementations by
other large companies. It happens to be an implementation I develop SW
for so I have had to learn about it. Still, one doesn't expect Kenny to
know about such things, or admit such knowledge if it is inconvenient to
his trolling.

>> Technically right, I suppose, but, obviously, from the POV of any sane
>> person, utter BS.
>
> So astronomers are not sane. How interesting.

They may well be, I have no evidence on the matter, but it does not
prevent them from being correct
--
Flash Gordon

In article <K->,
Richard Heathfield <> wrote:
>[Just debunking some trollschildt]
>
>Kenny McCormack said:
>
><snip>
>
>> You're the sort who would tell someone that the phrase "The sun rises in
>> the East" is incorrect/worthless/immoral/fattening because of the
>> possibility that there might exists planets/worlds in which it doesn't
>> hold.
>
>It's incorrect for Venus, for example.
>
>> Technically right, I suppose, but, obviously, from the POV of any sane
>> person, utter BS.
>
>So astronomers are not sane. How interesting.

Because anyone with a lick of common sense (something mostly missing in
the regs of this ng) knows perfectly well that the phrase is meant to
apply to this world (aka, the Earth) - the only planet that has any
human life on it - i.e., anyone to notice or care about the sun rising.

Obviously, the nit-shits of this ng will find a way to pick at that, too.

Kenny McCormack:

> Because anyone with a lick of common sense (something mostly missing in
> the regs of this ng) knows perfectly well that the phrase is meant to
> apply to this world (aka, the Earth) - the only planet that has any
> human life on it - i.e., anyone to notice or care about the sun rising.
>
> Obviously, the nit-shits of this ng will find a way to pick at that, too.


Yes, and that's because you weren't specific enough.

On comp.lang.c, the topic tends to be _very_ broad, given that we don't
talk about any one implementation in particular. If you want to talk about
machines which have 8-Bit bytes, then you'll had to introduce that as a
precondition to the discussion. If you don't produce that precondition,
then everyone is right to correct your false assumption that CHAR_BIT==8.

In every day speech, like Billy talking to James over a cup of coffee,
there's nothing wrong with saying that the Sun rises in the East, just like
there's nothing wrong with assuming 8-Bit bytes on a Windows programming
newsgroup.

This newsgroup deals with the C programming language in its most basic
form, the form described by the C Standard. The C Standard gives freedom to
implementations, even if these freedoms are only exploited rarely. For
instance, the C Standard gives freedom to the implementation to have any
size bytes (over 7 bits of course), but I think only a very small
proportion of implementations actually depend on this freedom.

If you're in an astronomy newsgroup, I wouldn't suggest saying that the Sun
rises in the East. It's not to bad an idea though if you're in an Earth-
related newsgroup though.

--

Frederick Gotham

Frederick Gotham wrote:
>
.... snip ...
>
> If you're in an astronomy newsgroup, I wouldn't suggest saying that
> the Sun rises in the East. It's not to bad an idea though if you're
> in an Earth- related newsgroup though.

Since East describes the direction from which the sun rizes, I
would expect it to be unambiguous for all worlds orbiting about a
single sun and having a rotation.

--
Chuck F (cbfalconer at maineline dot net)
Available for consulting/temporary embedded and systems.
<http://cbfalconer.home.att.net>