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

[Jussi Lahtinen]

Yes.
My big project is mainly executable, but the same time it act as library
for data editors etc tools. You can use the export command for as many or
few classes as you like. Very useful feature.


Jussi

On Wed, Jun 13, 2018 at 3:48 PM, T Lee Davidson <t.lee.davidson at gmail.com>
wrote:

> Thank you for that clarification, Jussi.
>
> At the time, I was going by the documentation at
> http://gambaswiki.org/wiki/doc/library#t3 . But now in re-reading it,
> either
> it's been recently edited, or I read something into it that simply isn't
> there.
>
>
> So then, ultimately, a library project can utilize as many modules as the
> developer deems necessary, and testing can be done as
> with any normal Gambas project.
>
>
> --
> Lee
>
>
> On 06/12/2018 06:29 PM, Jussi Lahtinen wrote:
> > 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
>
> ----[ 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/278bd83b/attachment-0001.html>