[fpc-pascal] Re: Get all caller adresses of a given function/procedure before executing

Rainer Stratmann RainerStratmann at t-online.de
Wed Aug 15 10:49:21 CEST 2012

Am Wednesday 15 August 2012 10:20:34 schrieb Reinier Olislagers:
> On 15-8-2012 10:08, Rainer Stratmann wrote:
> > Yes, that is possible as I understand it so far.
> > I did not know (dx)gettext before so replication is may not the right
> > word.
> Yes, it is. Replication is doing the same thing twice, regardless of the
> reasons/knowledge behind that fact.

I you want call it replication.

> > My solution will be more flexible I assume.
> > I put already some hours in it and I like to write my own code so I
> > follow the already driven way.
> I haven't used dxgettext, but would ask you to have a serious look at
> it. Presumably dxgettext users/developers had many of the same problems
> you face and have created solutions for those problems over the years.
> I understand you take pride in your own code and it feels like wasted
> effort to dump it, but using a set of proven code may be advantageous.
> You can still submit your own improvements to dxgettext if you hit
> problems... and if those aren't accepted, in the worst case create your
> own fork.

My style of coding is normally in general writing an own solution.
So I did it with a webserver also. Advantages are the flexibility. And a 
disadvantage is may the longer time to find a solution. But this fact 
relativizes the more specific the solution will be. I made the experience 
that the spent time will be the same (or even less if you exactly know what 
is needed) then.

If you are searching for an individual solution that is not done before than 
you have to ask the developers and hope that they support you. If not you 
have to find yourself a solution.

> You already have a very good grasp of the issues involved as you were
> writing your own solution. You could probably improve dxgettext with
> some things and get that in the main development tree, thereby improving
> things for others.

As I read now here
gettext seems already to be a (very) good solution. I am wondering why there 
are some problems with as I read somewhere in this thread.

> The other way round also works: other peoples' improvements can end up
> in your code for free (almost: you'll need some
> implementation/verification time).
> While this may all be very well known to you, I would ask you to step
> back and consider it: having a detached look at it may lead to a better
> choice.

For me it would be interesting to know how dxgettext gets the snippet 
information from the program code...!

> Just my 2 cents,
> regards,
> Reinier
> _______________________________________________
> fpc-pascal maillist  -  fpc-pascal at lists.freepascal.org
> http://lists.freepascal.org/mailman/listinfo/fpc-pascal

More information about the fpc-pascal mailing list