Re: The Lib debate

From: Betov (betov_at_free.fr)
Date: 02/09/04 

Date: 09 Feb 2004 00:28:37 GMT

Gerhard W. Gruber <sparhawk@gmx.at> écrivait
news:vdbd2059bsf6aku5s8um9pvdv4qref8h0i@4ax.com:

> On 08 Feb 2004 20:43:13 GMT wrote Betov <betov@free.fr> in
> alt.lang.asm with <XnF9489E0B0BC84Ebetovfreefr@212.27.42.71>
>
>>Calling Functions in a DLL is a comletely different thing.
>>There is not much logical difference between calling to a
>>Win32 DLL or calling to a DOS Interruption, or even, runing
>>an external Application.
>>
>>In all case, this is calling for something external to your
>>Application, that is supposed to do the work it is supposed
>>to do. Period.
>
> Which is exactly what a static library does.

No. The thing _is_ inside your dead File.

>Logically there is
> absolutely NO difference between a call into a copied function, a
> function imported from a static library, or a function imported via a
> shared object library (aka DLL in Windows). Oh! There is a small
> difference. For shared object libraries you have to call
> ldopen/LoadModule/GetProcAdress before you can even start using the
> function in case you import at runtime. If you statically link your
> so/DLL then you don't have to worry about this, because OS system
> loader will do this for you (or does it the startup code in C?, I'm
> not sure about this detail).

The difference is that, in case of DLL, you call for
something external, whereas with libs, you make use
of Blind programming for developing _your_ own App.
If so, there is no reason for writing Assembly.

>>The case of Lib is weird because it is neither external nor
>>internal. Plus it is based on the fancyfull idea that there
>
> From a logical point of view it ist an internal function where you
> happen to have no sourceode at assembly time available.

This is the problem. Not having _YOUR_ Source available,
in Assembly is something absolutely impossible. (Again,
as some seem to not understand what i am talking about:
"In what i call Asm", that is, in full Assembly written
App, developped by guys thinking Assembly).

>>do effectively exist some "reusable coding". In fact, _yes_
>>"reusable coding" _may_ exist, but the cost of it makes it
>>utterly incompatible with the Assembly ways of programming.
>
> Show me your implement of OpenGL.

??? Just take a look at a RosAsm user Demo for OpenGL...

>Ever used something like zip,

I have been told that zip comes with a Lib only. So, zip
cannot be use in Assembly until the day somebody write
what we need. GPL, please... :))

> CRC32
> calcluation,

??? You need a Lib for doing this ???...

> [...]
>>this make me laugh a lot...), he is doing _Basic_, with a
>>Tool that is far from achieving any of the actual Basic
>>performances.
>
> I don't understand why you think that a function, which is designed to
> do a special thing good, makes it better just because you happen to
> call it directly from source? If you copy and paste in some code, then
> this is exactly the same as if you would call a BASIC function either.
> What makes my CRC32 calculation different if I import it from a
> library, that I have even written myself, over the exact same code
> pasted into the sourcefile?

There are several points:

1) Usually, the available Libs written in Asm are buggy.

2) In a dedicated IDE like RosAsm, this would break
down several very important functionalities.

3) If we can do it the Assembly way, as well, i don't
see why we sould use an obsolete and Asm-incompatible
Method.

4) In RosAsm the Clip Functionalities are much more
powerfull, flexible and simple to use than the old
Lib Method.

5) Same as 4) with "PREPARSE IncInclude" for complete
Modules.

Betov.

< http://betov.free.fr/RosAsm.html >

Relevant Pages

  • Re: Static Libraries and Assembly Language
    ... My experience with asm is from about 14 yrs ago, ... actual Processors and Assemblers. ... compile time or at .lib creation time. ... Every Zip API I've ever seen comes with a dll. ...
    (alt.lang.asm)
  • Re: using the CWegPage.dll
    ... It is using the WINAPI (_stdcall) calling ... > The source code for the DLL is on that page and is in this link to the zip ... >> change the calling convention to that which VB can handle. ... >>> The goal is to put an internet explorer web browswer on my form. ...
    (microsoft.public.vc.language)
  • Re: using the CWegPage.dll
    ... It is using the WINAPI (_stdcall) calling ... > The source code for the DLL is on that page and is in this link to the zip ... >> change the calling convention to that which VB can handle. ... >>> The goal is to put an internet explorer web browswer on my form. ...
    (microsoft.public.vb.winapi)
  • Re: The Lib debate
    ... >Win32 DLL or calling to a DOS Interruption, or even, runing ... For shared object libraries you ... CRC32 ...
    (alt.lang.asm)
  • Re: #pragma lib buggers everything up
    ... > derive the client application's classes from the classes in the lib, ... to link the final executable (be it an EXE or a DLL) and it turns out ... there's no problem discarding unused functions at this ... and derived class is very fragile - it depends on a particular compiler, ...
    (microsoft.public.vc.language)