On 09/23/2014 03:55 AM, Boian Mitov wrote:
Because none of those is a strong typed language.
Each language has weak and strong points.
Pascal is semi strong typed language, and as such is very well
declarative style oriented.
Functional programming however merges very well with strong typed
dec
On 09/23/2014 11:31 AM, Giuliano Colla wrote:
Il 23/09/2014 02:24, John Briggs ha scritto:
Sven
At the risk of starting a flame war I have been pondering this question
since these threads have started:
Why has there been so many messages on this list debating the pros
and cons
of reference co
On 09/28/2014 08:58 PM, Lag Programming wrote:
@Nikolay
Thank you for your answer. :) Now that you've answered, can you
further respond to the following question: why is it needed to zero
fill the memory allocated that exceeds the requested value?
a) "pointer:=allocmem(initialsize);
realloc
On 28.09.2014 21:00, Constantine Yannakopoulos wrote:
Hi Sven,
On Sat, Sep 27, 2014 at 7:33 PM, Sven Barth mailto:pascaldra...@googlemail.com>> wrote:
Huh? Delphi really prohibits such things inside the destructor?
Would you mind to share an example (possibly including error
messa
Hi Sven,
On Sat, Sep 27, 2014 at 7:33 PM, Sven Barth
wrote:
> Huh? Delphi really prohibits such things inside the destructor? Would you
> mind to share an example (possibly including error messages), please?
>
Sorry, I wasn't clear enough.
With "prohibits" I didn't mean that you get a co
@Nikolay
Thank you for your answer. :) Now that you've answered, can you further
respond to the following question: why is it needed to zero fill the memory
allocated that exceeds the requested value?
a) "pointer:=allocmem(initialsize); reallocmem(pointer,increasedsize);". I
don't see the ben
On 09/28/2014 05:45 PM, Lag Programming wrote:
Hi! I need some help in understanding three things viewed in heap.inc.
...
3) I'm not interested in the importance of the presented function. Why
the "existing" code design is preferred over "alternative" code?
Existing code:
function SysAlloc
Hi! I need some help in understanding three things viewed in heap.inc.
1) Why is variable "heap_lock_use" declared as "integer"? Apparently this
variable never gets a negative value. Also, this variable never gets used as a
parameter to a function/procedure call that would require a transform
