On Dec 8, 2017, at 2:00 PM, John Baughman wrote: > Is anyone else getting a bit annoyed at the changes in typing behavior in the > latest R release? I am getting many syntax errors in interpreted mode that I > did not get in prior versions. SET QUERY DESTINATION(Into > Variable;$foundCount), for example will throw a runtime error in interpreted > mode if $foundCount is not explicitly typed.
I’ve not done any compiler work in R releases that required compiling. Just curious, what is your compiler setting for the structure? Is it all variables are typed? If so, try turning that down to let 4D type all variables to see if the runtime error still occurs. If 4D is using this compiler setting I think it is a great idea. The more they can make the runtime environment work the same as the compiled environment the better. Same runtime errors would be great. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 [email protected] ******************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
