Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Compatibility issues between Windows and Unix?

compatibility Unix Windows
0
Posted

Compatibility issues between Windows and Unix?

0

Here, ‘Unix’ stands for any POSIX-like operating system such as Linux, Mac OS X, Solaris, etc. package.config is a string where the first ‘character’ is the directory separator; so package.config:sub(1,1) is either a slash or a backslash. As a general rule, try to use this when building paths. A big difference between the Windows and Unix builds is that the default package.path is based on the location of the Windows executable, whereas on Unix it is based on /usr/local/share/lua/5.1. It is therefore easier to do a local user install of Lua on Windows, but Lua respects the environment variables LUA_PATH and LUA_CPATH. Lua depends more directly on the system’s C runtime libraries than most scripting languages so you have to appreciate platform differences. Use the “rb” specifier with io.open if you need compatibility with Windows binary I/O. Be careful of os.tmpname because it does not return a full path on Windows (prefix with the value of the TMP environment variable together with a b

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123