Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
I just finished checking all custom constants for: duplication between component and host custom constants as well as checking the custom constants against duplication of 4D constants, host and component method names No duplication was found. still looking for ideas CHip On Wed, 2 Oct 2019

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
Beat you to that idea I have done a check for that. symbol tables from both host and component cross checked against the other's methods On Wed, 2 Oct 2019 20:11:18 +0200, Peter Bozek wrote: > On Wed, Oct 2, 2019 at 7:37 PM Chip Scheide via 4D_Tech < > 4d_tech@lists.4d.com> wrote: > >>

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Peter Bozek via 4D_Tech
On Wed, Oct 2, 2019 at 7:37 PM Chip Scheide via 4D_Tech < 4d_tech@lists.4d.com> wrote: > Repair, Compact, Repair of Host structure, and Repair of Host data file > Does not solve the problem. > > Chip > This is rather very far-fetched idea, but once I run into similar problems when I had a

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
Repair, Compact, Repair of Host structure, and Repair of Host data file Does not solve the problem. Chip P.S >and there are no variables in > the host which have a host method name. Should read: and there are no variables in the component which have a host method name. On Wed, 2 Oct 2019

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
I also created the symbol table for both host and component, and checked that there are no variables which have the same name as any method in both. I.E. there are no variables in the Host which have the same name as either the host, or component's methods, and there are no variables in the

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
good idea! I'll try and report back THANKS! On Wed, 2 Oct 2019 14:36:05 +, Keisuke Miyako via 4D_Tech wrote: > I don't think the events are relevant in this instance. > > what if you create a copy of the component and make all methods > private (don't share with host) ? > > would you still

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Keisuke Miyako via 4D_Tech
I don't think the events are relevant in this instance. what if you create a copy of the component and make all methods private (don't share with host) ? would you still get the error? if the error stops, you know that a shared method is being invoked. in that case, you can add a trace at the

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Chip Scheide via 4D_Tech
> perhaps you can export the symbols file and see if there are any > global symbols (process variable, project method) that could be > invoked unintentionally. > > it sounds like a method is being called recursively. I agree with this assessment - except - the stack overflow error occurs

Re: Difference between loading a compiled and interpreted component

2019-10-02 Thread Keisuke Miyako via 4D_Tech
perhaps you can export the symbols file and see if there are any global symbols (process variable, project method) that could be invoked unintentionally. it sounds like a method is being called recursively. ** 4D Internet

Difference between loading a compiled and interpreted component

2019-10-01 Thread Chip Scheide via 4D_Tech
What is executed, or not, when loading a compiled component vs an interpreted component? --- Gas is for washing parts Alcohol is for drinkin' Nitromethane is for racing ** 4D Internet Users Group (4D iNUG) Archive: