On Sun, Jun 20, 2010 at 09:36:25AM +, Mark Morgan Lloyd wrote:
> > FPC loads foreign libraries externally all the time. But you also don't
> > communicate on Pascal level between with them, and keep the RTL/libc states
> > totally apart.
> >
> > I refer to this as the "manual" solution. (which
Marco van de Voort wrote:
FPC loads foreign libraries externally all the time. But you also don't
communicate on Pascal level between with them, and keep the RTL/libc states
totally apart.
I refer to this as the "manual" solution. (which is btw not as easy as many
people think, specially for la
Dear Michael,
...
For example, Packages share the same memory space and class
inheritance tree.
Libraries do not.
You're absolutely right.
Your example will fail for instance when using strings, exceptions and
classes.
Yes, the example will fail for classes and exceptions. You are correct.
B
On Sat, Jun 19, 2010 at 12:34:34PM +, Mark Morgan Lloyd wrote:
> > For example, Packages share the same memory space and class inheritance
> > tree.
> > Libraries do not.
>
> Thanks both. So if I understand things correctly:
>
> * A package uses the same LCL as the rest of the app.
Yes. Bot
Michael Van Canneyt wrote:
For example, Packages share the same memory space and class inheritance
tree.
Libraries do not.
If you are using packages, then TComponent will be defined in the rtl
package, and both the application and program will refer to the same
definition in the rtl package,
On Sat, 19 Jun 2010, Thierry Coq wrote:
Hello,
I was assuming that something like that would be needed for the dll/so, but
the particular point I'm interested in is whether the main app /has/ to be
restarted, or if there are hacks that can get around that.
which suggests that there are lim
Hello,
I was assuming that something like that would be needed for the
dll/so, but the particular point I'm interested in is whether the main
app /has/ to be restarted, or if there are hacks that can get around
that.
which suggests that there are limits as to what can go into a dll/so.
In
Alexsander Rosa wrote:
My ERP has an auto-update feature in the main application (called
"rnge2.exe"). The app does the following steps:
1) Check if there's a newer version. The new releases are replicated to
each customer's branch.
2) If there's a newer version, download, md5sum-check and ren
My ERP has an auto-update feature in the main application (called
"rnge2.exe"). The app does the following steps:
1) Check if there's a newer version. The new releases are replicated to
each customer's branch.
2) If there's a newer version, download, md5sum-check and rename to
"rnge2.new"
3) E
To what extent could a Lazarus app replace itself with a new version
without interruption?
For example, if the main form had a menu at the top, synedit with popups
and a status bar at the bottom, presumably much of the "intelligence"
could be moved into dll/so libraries which could be closed a
10 matches
Mail list logo
