Am So, den 13.03.2005 schrieb Jeff Pohlmeyer um 00:03:
[..]
> > > Maybe I'm too used to using Delphi, where such things
> > > are hidden from the developper.
>
> > That's the nice part of Delphi.
>
> You are talking about searching the system for object
> files generated by another compiler and
mm wrote:
compute !1, i.e., Factorial 1. Currently, all you have
Of course, I should have written "1!" and not "!1".
mm
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
I still don't understand what sort of c "package" you have
that generates a bunch of object files, but doesn't create
a shared library or static archive.
Does it have its own makefile or configure script?
Sometimes adding --enable-shared or --enable-static
to configure will tell it to build a li
Micha Nelissen wrote:
In this case I would advise not to free the pointer and explicitly document this choice in the freepascal documentation. (As the user can free the area himself anyways, but can not bring it back).
Yes, exactly.
Maybe it would help you more to allocate more space in advance?
On Sat, 12 Mar 2005 21:46:15 +0100
mm <[EMAIL PROTECTED]> wrote:
> Micha Nelissen wrote:
>
> >The problem with your approach is: how do you know whether the memory
> >was extended, or left alone because there was no memory available to
> >extend it ? In general, shortage of memory produces a runt
Micha Nelissen wrote:
The problem with your approach is: how do you know whether the memory was
extended, or left alone because there was no memory available to extend it ? In
general, shortage of memory produces a runtime error, but this is configurable
by a global var.
No, that's easy. If the
Am Sa, den 12.03.2005 schrieb Koenraad Lelong um 18:53:
> Jeff Pohlmeyer wrote:
> >>My question : is the linker not smart enough to find out
> >>by itself where to look for those missing object files ?
> >
> >
> > Not sure if I understand your question, but as Marc already
> > mentioned, you ca
On 12 Mar 2005, at 18:53, Koenraad Lelong wrote:
I assumed that when a routine uses some code in an object file which
in turn uses code in another object file, the linker would be smart
enough to know to look for that second object file.
No, the linker cannot know in which other object these rout
Jeff Pohlmeyer wrote:
My question : is the linker not smart enough to find out
by itself where to look for those missing object files ?
Not sure if I understand your question, but as Marc already
mentioned, you can control this with the -k-L compiler switch.
You can also control the way the co
> Original Message
> Subject: Re: [fpc-pascal] ReAllocMem problem (?)
> From:"Marcel Martin" <[EMAIL PROTECTED]>
> Date:Wed, January 19, 2005 0:57
> To: "FPC-Pascal users discussions"
> -
10 matches
Mail list logo
