Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Flávio Etrusco
On Sat, Jul 30, 2011 at 6:07 PM, Florian Klämpfl wrote: > Am 30.07.2011 22:54, schrieb Flávio Etrusco: Repeating myself, if there isn't something like CodeTools (i.e. only with text search) is way more difficult to search for operator declarations. >>> >>> Why? Searching for op

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Florian Klämpfl
Am 30.07.2011 22:54, schrieb Flávio Etrusco: >>> >>> Repeating myself, if there isn't something like CodeTools (i.e. only >>> with text search) is way more difficult to search for operator >>> declarations. >> >> Why? Searching for operator+ is no more difficult than for function add ? >> > > Blan

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Bernd
2011/7/30 Florian Klämpfl : > This is exactly what ref. counting solves? Did you read my other mail > regarding your problem with ref. counting? Yes, of course Ref counting "solves" it (in the sense that it can all be made to work as expected and not leak memory) and your suggestion of checking t

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Flávio Etrusco
>> >> Repeating myself, if there isn't something like CodeTools (i.e. only >> with text search) is way more difficult to search for operator >> declarations. > > Why? Searching for operator+ is no more difficult than for function add ? > Blanks and linebreaks... Of course if one always use the sam

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Florian Klämpfl
Am 30.07.2011 19:27, schrieb Bernd: > 2011/7/30 Florian Klaempfl : > >> The automatic constructor/destructor concept of C++ causes the same >> overhead. And the overhead for a function or operator overloading based >> approach is the same imo. Or do you have any example where a function >> based a

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Florian Klämpfl
Am 30.07.2011 18:28, schrieb Flávio Etrusco: >>> >>> And there is another advantage of using procedures/functions instead of >>> overloading operators: >>> You can search for the procedure to look what it actualy does. >> >> Not if you use function/procedure overloading. Then the situation is >> ex

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Jorge Aldo G. de F. Junior
Imagine the following : A -> C -> E B -> D -> E A is ref counted, and says that theres 10 references to the object C B is ref counted, and says that theres 5 references to the object D But both C and D points to the same object ! So now you have actually 15 references to the same object. Lets

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Jorge Aldo G. de F. Junior
if i understand correctly, your problem is not operator overloading or whatever in the language. You have references. Now you want to write counted references to references and deal with this in the overloaded operators your problem is right into the counted reference to reference. A := B makes

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Bernd
2011/7/30 Florian Klaempfl : > The automatic constructor/destructor concept of C++ causes the same > overhead. And the overhead for a function or operator overloading based > approach is the same imo. Or do you have any example where a function > based approach performs better? Overloaded operator

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Flávio Etrusco
>> >> And there is another advantage of using procedures/functions instead of >> overloading operators: >> You can search for the procedure to look what it actualy does. > > Not if you use function/procedure overloading. Then the situation is > exactly the same as for operators. > Repeating myself

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Florian Klaempfl
Am 29.07.2011 13:43, schrieb Bernd: > > With interfaces and their reference counting it can be made to work > but the cost of doing this seems so immense that I don't believe it is > justifiable in many real world applications (at least not in my > application). The automatic constructor/destruct

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Florian Klaempfl
Am 30.07.2011 17:05, schrieb Jürgen Hestermann: >> > Say for instance you are working on Galois fields and you have to do > arithmetic on the elements like this: >> > g1 + g2 / g3 >> > If you don't have operator overloading, you have to do it with > functions, like this: >> > gf_add(g1, gf_div(g2,

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Jürgen Hestermann
> > Say for instance you are working on Galois fields and you have to do arithmetic on the elements like this: > > g1 + g2 / g3 > > If you don't have operator overloading, you have to do it with functions, like this: > > gf_add(g1, gf_div(g2, g3)) > > This is not very readable, I'm sure you wil

Re: [fpc-pascal] Re: operator overloading and counting references / creating / destoying anonymous instances

2011-07-30 Thread Jürgen Hestermann
Henry Vermaak schrieb: >> I think operator overloading is a pain. As you said: What is the >> advantage? For me operators should be defined by the language only > It improves readability, making it more logical. Just the opposite! It hides important imformation for the reading person. > Say