Ini functions should be documentated as containing limitations

[lwc]

There's an old feature request #15 about fixing the various limitations of the Ini functions (what's not mentioned there is that they sometimes throw an @error when their target is called Autoinf.inf).

But I have a different feature request - just document the fact that there are limitations, to avoid confusion.

Do functions like FileRead not suffer from such limitations because they are custom made by AutoIt, while Ini functions use Windows API? If so, mention this officially. For example:

IniReadSectionNames

Remarks
Note that Ini functions rely on Windows API which suffers from various limitations.
This situation shall remain as Microsoft asked to use other storage methods.
Custom UDFs that bypass the limitations can be found on AutoIt's forums.

[TicketCleanup]

Automatic ticket cleanup.

[BrewManNH]

I'm fairly certain that the only limitation on reading an INI file is in reading a whole section, not the names of the sections. The limitation is already in the help file for IniReadSection. There's also another limitation in INI files that they're supposedly only capable of holding around 38K of data.

INF files are not INI files, although they're formatted alike. INI files have no structure other than sections and key/value pairs. INF files are used for installing software or drivers and have a set structure.