in principle (that is, if we just focus on the version number) then a v13 compiled component will work in v14 all the way up to v16.
but there are other factors to consider. if you intend to also compile your host application, you need to be aware that non-unicode mode is not available in 64-bit (if the component is non-unicode) and Mac 64-bit compilation requires the new (14R3 or above) compiler. http://doc.4d.com/4Dv16R4/4D/16-R4/Architecture-of-64-bit-applications.300-3330499.en.html and the standard distribution of 4D v16 on Mac is now 64-bit. a v13/14 compiled component would be limited to 32-bit on Mac. http://doc.4d.com/4Dv15/4D/15.4/Component-installation-and-compatibility.300-3285444.en.html so to fully target v15, you should compile with the 64-bit option on v15. -- you might also want to consider that v15 pointers have a different internal representation, which is mostly handled transparently, but does alter the behaviour of some functions: http://doc.4d.com/4Dv15/4D/15/Unicode-mode-for-methods.300-2018652.en.html 2018/02/02 6:34、Chip Scheide via 4D_Tech <4d_tech@lists.4d.com<mailto:4d_tech@lists.4d.com>> のメール： Given a component, compiled in v13, besides v13, which version(s) will component work with? Repeat for v14, v15 ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
