static locals are treated as globals, except for scope checking by the compiler. Yes, that was my first approach. The problem is that it exhibits the exact same behaviour (I tried using features to inhibit double invocations). I'd like to know more about this issue to understand why it happens. "Douglas I. Anderson" wrote: > ..and static locals are treated as globals if I'm not mistaken, so static > locals are also not allowed in DA's. > > Solution: use the feature manager (FtrGet and FtrSet). > -- Sergio Carvalho --------------- [EMAIL PROTECTED] If at first you don't succeed, skydiving is not for you
- Desk Accessories and static variables Sergio Carvalho
- RE: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- RE: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Anonymous
- Re: Desk Accessories and static variables Sergio Carvalho
- Re: Desk Accessories and static variables Douglas I. Anderson
