OpenEuphoria

Re: Win32Lib overhead

• Posted by Derek Parnell <ddparnell at bigpond.com> Nov 28, 2002
• 388 views

Hi Greg,

----- Original Message -----
From: <g.haberek at comcast.net>
To: "EUforum" <EUforum at topica.com>
Subject: Win32Lib overhead


>
> Hi All,
>     If I write a program using Win32Lib, then translate
> and compile it, will there be an over head from all the
> declarations and routines in win32lib.ew? I'm trying to
> make my programs extremely portable, and some of them
> come out to be in the range of 200K for faily simple
> apps.
> I guess what I'm really asking is "Is Win32Lib or
> direct API coding better?"
>

By "portable" I assume you mean "small enough to fit on a diskette".

With the current monolithic win32lib.ew approach, any bound program is going
to be a minimum of 160K. This is due to the inclusion of many routines and
identifiers that may not be being used by your app. This effects size and
not speed of course.

In future, you will have more opportunity to mix-and-match the win32lib
functionality to your apps requirements, giving you the possibility of
leaving out those elements that you are not using.

As I see it, the benefits of the win32lib and Andrea Cini's execellent
euwingui library, is that it is easier to create and maintain programs with
these - at the cost of size and execution speed.

Going with the WinAPI approach, you will certainly be able to create smaller
and faster executing programs - at the cost of more of your time to create
and maintain them. Overtime, however, you will also be able to build up a
collection of files to make your own "win32" library - rather than
reinventing the wheel for each new app.

However, if you are really serious about making small Win32lib apps, you
should take a look at Masm32 - an excellent way of producing assembler based
win32 apps.

----------------
cheers,
Derek Parnell