Tim,
a bit late but...
There are other reasons, but one is:
Thread safety :)
And while this is NOT an issue in v13, I am writing this code now, I
might as well make as much of the code thread safe, and future proof,
as is reasonable.
Using 4D functions requires wrapping an On Err Call("method") On Err
Call("") around the various disk access functions.
ex:
On Err Call("File_Errors")
Delete Document($Document)
On Err Call("")
Unless there is some way I am unaware of -- very possible :)
the only way to get information BACK, such as what error occurred, from
the On err call method(s) is via IP var(s).
Using LEP the calls for Disk access are natively thread safe (at least
I would expect so -- NOT tested), and
also they are MUCH faster.
The 4D code, in which LEP is called is (I believe) thread safe as most
of the 'work' is text manipulation.
BTW: is there a list of either (or both) thread safe, and/or Thread
unsafe 4D commands?
Thanks
Chip
On Fri, 20 Apr 2018 22:01:32 +0000, Timothy Penner via 4D_Tech wrote:
> Why use LEP for something that has been built into 4D since v6?
> http://doc.4d.com/4Dv15/4D/15.5/MOVE-DOCUMENT.301-3576481.en.html
>
> -Tim
>
>
>
---------------
Gas is for washing parts
Alcohol is for drinkin'
Nitromethane is for racing
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************
