Hello Brian,
Yes, please send the diff file, so I can look at it. Which platform
(Windows, Linux, FPC) are you using?
Another approach would be to look at (and reverse engineer) the byte
code. If it's not obfuscated, it might even be easier to parse and port
than the native Java.
On
On Wed, 2010-10-27 at 20:07 -0700, leledumbo wrote:
Where do these methods go?
protected function TCustWebApplication.WaitForRequest(out ARequest :
TRequest; out AResponse : TResponse) : boolean;
protected procedure TCustWebApplication.EndRequest(ARequest :
TRequest;AResponse : TResponse);
On Thu, 2010-10-28 at 14:16 +0200, Joost van der Sluis wrote:
On Wed, 2010-10-27 at 20:07 -0700, leledumbo wrote:
Where do these methods go?
protected function TCustWebApplication.WaitForRequest(out ARequest :
TRequest; out AResponse : TResponse) : boolean;
protected procedure
Thank you, What techiniques have you used in the past that you could
share to get me started?
On Wed, Oct 27, 2010 at 8:04 PM, leledumbo leledumbo_c...@yahoo.co.id wrote:
Learn compilation technique, a recursive descent parser should be easy to
understand and code instead of learning automatic
Jonas wrote:
export MallocStackLogging=1
Then, once the program is running and has leaked memory, run
leaks nameofyourprogram
Thanks for this tip! It is very interesting, however in this situation
it does not detect the lost memory.
At this point I have to give up on GetTextWidth - I will
Brian Winfrey bwcod...@gmail.com wrote in
message news:aanlktinq5bgnulg05nyuizl8bpoxdenu3ofyuqhnp...@mail.gmail.com...
Thank you, What techiniques have you used in the past that you could
share to get me started?
On Wed, Oct 27, 2010 at 8:04 PM, leledumbo
leledumbo_c...@yahoo.co.id wrote:
Then, once the program is running and has leaked memory, run
leaks nameofyourprogram
Thanks for this tip! It is very interesting, however in this situation
it does not detect the lost memory.
At this point I have to give up on GetTextWidth - I will avoid it for
now. Maybe next year the
