As far as I know, the calls are correct, but it may be that ansistrings are messing up the stack.

It also is possible that method calling is buggy, I know Florian is currently doing some work in that area... It's probably connected with 2 other bugs reported by Nicolas and Michael Hess..

Michael.

I am having a terrible time with lost object references.

as long as i access a object in the same procedure everything is cool.

if I access it from the next procedure it is still assigned but throws access violations. What the workd is going on here.

I have to believe it is the compiler the calls are correct.

Cliff

I know I am thinking it may be fixed already.

I will run a make cycle on it after downloading source tonight..

Cliff

But the problem with the 'message' thing (the code michael VC) posted here is still there and crashes the compiler.

Peter

Hello,

It also is possible that method calling is buggy, I know Florian is currently doing some work in that area... It's probably connected with 2 other bugs reported by Nicolas and Michael Hess..

Peter reported yesterday (sunday) that this problem is corrected. I downloaded cvs sources, rebuilt the compiler and got running basic test. It works now!! :)

I haven't been able to link my gtk test, though. But the problems seemed related to gtk libs... I couldn't get through yesterday nor I will today :(

Anyway, great!
I would update compiler to lastest cvs sources before trying anything else related to "procedure of object".

greetings

Nico