[Gambas-user] Creating a library....

[Jussi Lahtinen]

Lee, this was the reason of the criticism.

You said *"As I understand it, for final deployment, you should not have a
Main module _and_ a library module"*.

This is wrong.

You said *"The Main module should be your library"*.

This is misleading, as it doesn't matter at all.

You said *"For testing, create a new project that uses the compiled
library"*.

This is not the same as include unit test within the library. And even if
the development ends, the test should not be removed as you might still
want to maintain the library. Note that libraries can be run as normal
executables, if they have start up method.


Jussi






On Tue, Jun 12, 2018 at 3:56 PM, T Lee Davidson <t.lee.davidson at gmail.com>
wrote:

>
>
> On 06/11/2018 05:22 PM, Christof Thalhofer wrote:
> > Am 11.06.2018 um 22:44 schrieb Jussi Lahtinen:
> >>     I went by the documentation. If it is wrong, then the documentation
> >>     needs correction?
> >>
> >>     You have said almost the same as I have. Which part, exactly, is
> >>     incorrect?
> >>
> >>
> >> There is no reason to remove the Main module ever. Ready product or not.
> >
> > Yes. And a methods of a lib can easily been tested from inside the same
> > project.
>
> As I said could be done for development purposes.
>
> > There is no reason to create an extra project to test the library.
>
> Again, as I stated the testing could be done within the same project. But,
> how would one test that the compiled and installed
> library works with a different project?
>
> (And, BTW, I never said to remove the Main module.)
>
>
> --
> Lee
>
> ----[ Gambas mailing-list is hosted by https://www.hostsharing.net ]----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gambas-basic.org/pipermail/user/attachments/20180613/880d19d8/attachment-0001.html>