GetMem 1x as Procedure, and 1x as Function - confused me

[paule32]

In the heaph.inc - there are:  https://www.freepascal.org/docs-html/rtl/system/getmem.html

you have "GetMem" twice.

- one Time a Procedure,
- one Time a Function with return Value.

My knowledge of other DSL's like C++ - so you can't have members with different return Values.
But you can have multiple overloaded members - with different Parameter's/Argument's.

What about FPC ?

[marcov]

Afaik for overloading, roughly the number of arguments must be different and/or typed different, as that is the signature used for which function to call. So not on the return type.

If the right version is chosen, on those criteria, it must then match the use for the rest of signature, including return value.

[paule32]

how about the function GetMem(size): Pointer ?
is that in context of the Memory Manager ?
where did GetMem "get" the Pointer, to allocate the Memory size ?

[marcov]

They both call the heapmanager's getmem.

[Thaddy]

You are free to write your own memory manager anytime. It is also easy. Not like your other questions which take a lot more effort..
Look at the code in cmem.pp

[paule32]

how can I "store" the Pointer's to "allocated" Object's ?
with a classic "linked List" ?

[Thaddy]

the linked list needs to be a doubly linked lst and store both allocation size and data (so a record) . Easy

[paule32]

record's are like class's ?

All what is in a record, is transparent/public ?
All what is in a class, can be private, public  ... ?

[Thaddy]

That has no relevance. Use records, before you can even use classes.

[Zoran]

All what is in a record, is transparent/public ?

That used to be true in old Pascal, but modern Pascal language has "advanced" (also called "extended") records. FPC implements advanced records since version 2.6.
To be able to use advanced records, you need the mode switch "advancedrecords".

The main difference between records and classes is that
  - class is always allocated on the heap and each class variable declared in your code is an implicit pointer. You have to allocate it (by using constructor) and it is programmer's (yours) responsibility to destroy it, before the pointer goes out of scope.
  - record variables are allocated like any variable of some fundamental type - a record can be allocated on the stack. If you want a record allocated on the heap, you need a pointer which is allocated in code (with standard procedure new) and deallocate it (with dispose).

Another difference is that records do not have inheritance.

[Zoran]

In the heaph.inc - there are:  https://www.freepascal.org/docs-html/rtl/system/getmem.html

you have "GetMem" twice.

- one Time a Procedure,
- one Time a Function with return Value.

My knowledge of other DSL's like C++ - so you can't have members with different return Values.
But you can have multiple overloaded members - with different Parameter's/Argument's.

What about FPC ?

It is so in FPC as well, you are right that two overloaded routines with same name and in same scope need to have different signature (argument list). And these two routines do have different signatures.
The fact that they have different return values would not be enough by itself, if the argument list were the same, they could not be overloaded.

[Thaddy]

Zoran, you are missing the point.
He is writing his own compiler so he needs to implement everything himself.
He is not very knowledgeable, so he should look at the basics first
Like here: https://secondboyet.com/Code/ToDADS_source.zip

Those are the basics, but for delphi. It still compiles, but not in his hands....

[cdbc]

Hi
@Thaddy: I don't think that, without Julian's writing, he'll get much out of the sources.... From what I've seen from him so far, he needs to buy the book.
Regards Benny

[Zoran]

He is writing his own compiler

Oh...

Zoran, you are missing the point.

Totally.