Re: interesting find

> -Original Message- > From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Timothy Penner via > 4D_Tech > Sent: Wednesday, February 20, 2019 4:31 PM > To: 4D iNug Technical <4d_tech@lists.4d.com> > Cc: Timothy Penner > Subject: RE: interesting find > &g

RE: interesting find

e- From: 4D_Tech <4d_tech-boun...@lists.4d.com> On Behalf Of Timothy Penner via 4D_Tech Sent: Wednesday, February 20, 2019 4:31 PM To: 4D iNug Technical <4d_tech@lists.4d.com> Cc: Timothy Penner Subject: RE: interesting find I have been telling people for years that the compiler gets s

RE: interesting find

I have been telling people for years that the compiler gets smarter in each new version. You may have a line of code that you thought was working, but in fact, it shouldn’t have worked at all, and the compiler may not have caught it before, but now it does. This is something I frequently tell

Re: interesting find

I have noticed the compiler in v17 is significantly better at flagging little errors like that. And a lot of others. There were some wonky things in a database I converted which is in active use, compiled, all vars typed. I thought v17 must have corrupted the code somehow because I just didn't

interesting find

I have found something in v17 that I did not think would work I have a method which is always passed a pointer. I made a mistake way back when in v15 The compiler declaration is c_pointer (method;$1) while in the method it was c_text. What is strange is that it has worked in v15 but in 17 it