[fpc-pascal] Re: Get all caller adresses of a given
function/procedure before executing
Jorge Aldo G. de F. Junior
jagfj80 at gmail.com
Thu Aug 16 13:24:01 CEST 2012
If passrc changes, so can ABI and whatever else method you use change too...
If i was going to start a project now with multilanguage suport i
would search for a existing solution or start a new project based on
I dont see how can searching for strings be so hard, you dont even
need a full fledged parser to do that... having passrc is handy
because its something standard and already done.
I believe such a tool written using passrc would limit itself to parse
each source file, put each string found into a global string list and
replace string instances with a call to a global function like
GetMyString() with the string entry numer as parameter...
I would even export such strings to an external file to allow fast,
on-the-fly, language selection...
IIRC this is called string pool.
but thats my two cents...
2012/8/16 Rainer Stratmann <RainerStratmann at t-online.de>:
> Am Thursday 16 August 2012 12:23:00 schrieb Jorge Aldo G. de F. Junior:
>> I still dont understand why dont you hack passrc and grab all the
>> strings from the source ?
> Because I have an almost finished solution. I worked already for a while on
> it. Some integrated piece of code is easier to handle for me than using a
> tool which requires (an) additional step(s) and may can change its behaviour
> in the future. In the last case even more (demotivating) work has to spend on
>> You can even replace them with identifiers and do all the resource
>> string mumbo jumbo automatically if you write a app to do this based
>> on passrc...
> This is more complex than own code that I know best and can change to my needs
> quickly if it there is a need for.
>> Actually, why theres no such tool included with freepascal already ?
>> (there is ?)
> fpc-pascal maillist - fpc-pascal at lists.freepascal.org
More information about the fpc-pascal