Hi Wayne,

Thanks for the idea. So far the symbols files has provided what I need. Not as 
simple to parse as if it had been spit out in JSON, but okay. Mostly I’m trying 
to get an idea of which of my “foundation” modules are not thread safe, but 
could be.


Synergy Farm Solutions Inc.
Aetna, AB Canada

> On Apr 11, 2019, at 4:37 PM, Wayne Stewart via 4D_Tech <4d_tech@lists.4d.com> 
> wrote:
> I can't find the db I did this in but what I did was this:
> METHOD GET PATHS(Path project method;$MethodNames_at)
> METHOD GET ATTRIBUTES($MethodNames_at;$Attributes_ao)
> Create a new array with those that area already marked as preemptive
> safe.  Save it somewhere
> Then use METHOD SET ATTRIBUTES to set them all to preemptive safe.
> Compile and enjoy all the errors coming in.
> You should be able to work through the list (slowly).
> If you run out of time reapply the original set of attributes from the
> initial call.
> Then repeat until you've got everything that is safe labelled that way.

4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com

Reply via email to