forum.vdsworld.com

dmonckton · Posted: Fri Mar 02, 2007 10:49 am Post subject: Including libraries

Hi

I have a large library of functions that I always include at the start of a new project. I only need a small number at a time. Does including loads of unused subroutines have any adverse effects on the final application?

Thanks

David.M

Hooligan · Posted: Fri Mar 02, 2007 1:51 pm Post subject:

Hi David,

That's known as bloatware... M$ does it all the time, it never bothers them!
Other than using up memory, it shouldn't hurt anything... (Unless the user doesn't have much memory available...)

Hooligan

DaveR · Posted: Fri Mar 02, 2007 1:55 pm Post subject:

I'm only guessing here... but "including" the dsc, dsu etc would only affect the executable's compiled size. But "defining" lots of unused commands and functions *may* have an adverse affect on memory use and runtime speed.

But what I would like to see is people sharing their libraries of user defined functions and commands (in the Visual DialogScript 5 Source Code forum - http://www.vdsworld.com/forum/viewforum.php?f=18 )

jwfv · Posted: Fri Mar 02, 2007 2:28 pm Post subject:

That is a great idea, Dave. I would like to see more of that as well. Heck, it might even make me actually code mine properly, comment the code, and share a few functions and subroutines!

dmonckton · Posted: Fri Mar 02, 2007 4:38 pm Post subject:

Then the only way to get round this is to define each library function on a separate line and rem it out when I don't need it!! This is a bit crap and I'm sure I'm going to rem out the wrong functions....

David.M

vdsalchemist · Posted: Sat Mar 03, 2007 2:01 am Post subject:

dmonckton,
I would say that you need a program that would do the following steps before you compile the Final Exe.

1) read your script and find all the functions and commands that are in your library.
2) build a library with just those functions.
3) change the #include statement in your script to reflect the new library.
4) compile your script and have a non-Micro$oft application.

Now to be honest with you most VDS Exe's don't get over a few hundred KBytes so I don't think it will be an issue on most PC's. The size of the script not only affect's the size of the Exe but also it's memory consumption. VDS is a true interpreted language. This means that every line is interpreted 1 line at a time. VDS does not translate the scrpt to some other form durring compilation.