'FileExistsUTF8" is deprecated: what to use then?

[frederic]

dear specialists
i get following warning:

laadunit1.pas(785,27) Warning: Symbol "FileExistsUTF8" is deprecated: "Use the function in LazFileUtils unit"

what is the name of the alternative fuction where this refers to?

frederic

[paweld]

FileExists

[frederic]

oh... simple,
i was used to use this in the past, and was forced to apply  the ....utf8 adapt and stayed with it since.
looking in LazfileUtils i only saw the old "fileexists" .
I return to the old function again and see .........what  comes i
thanks for the reaction
frederic

[Bart]

laadunit1.pas(785,27) Warning: Symbol "FileExistsUTF8" is deprecated: "Use the function in LazFileUtils unit"

FileExistsUtf8 function is in the LazUtf8 uit now.
It used to be in LCLProc of FileUtil unit.
Simply add LazUtf8 to your uses clause after LCLProc and/or FileUtil and your in the clear.

OTOH: as Paweld wrote, currently simply using FileExists (in Lazarus) should work, as long as the parameter is of type string (not UTF8String), and you did not define DisableUtf8RTL in your project options.
All this assuming you are not on Win9x, where (IIUC) you will still need the *UTF8() functions from LazUtf8.

Bart

[Thaddy]

Oh, so this is just part of the UTF8 Lazarus f*ck-up reconstruction excercise? I appreciate that.

[JuhaManninen]

Oh, so this is just part of the UTF8 Lazarus f*ck-up reconstruction excercise? I appreciate that.

What does that mean? What exactly is f*ck-up?
In my experience Unicode is now supported better than ever.
The answer from paweld was correct. Just use the Delphi compatible FileExists(). Is there something wrong with such a solution?
Bart's answer in this context was not useful, especially if it triggered your negative reaction. It listed 2 corner cases which most people can ignore.

Anyway Thaddy, please try to be more positive and constructive. It is not nice to always find something negative of things discussed.

[Bart]

Bart's answer in this context was not useful, especially if it triggered your negative reaction. It listed 2 corner cases which most people can ignore.

Please don't be so harsh on me.
My answer to the original question is the correct one from the perspective of the given message, except that where I wrote LazUtf8, you are supposed to read LazFileUtils.
If you want to use FileExistsUtf8, you are now supposed to call the one from LazFileUtils.

The suggestion to uses FileExists is not an answer to the question "what is the name of the alternative fuction where this refers to?", where this refers to the  "Use the function in LazFileUtils unit" part of the compiler message.

That being said: using FileExists instead of FileExistsUtf8 is the future way to go.
In almost all use cases there is no need for the UTF8 file functions anymore.

B.t.w. I like corner cases 

Bart

[Bart]

Oh, so this is just part of the UTF8 Lazarus f*ck-up reconstruction excercise? I appreciate that.

Excuse me?
I feel offended by that remark.
In the past we have worked very hard to have unicode support in file functions.
Before the 3.0 series compiler this was not possible using standard fpc libraries. We had to explicitely translate UTF8 encoded strings to WideString (Windows platform) just to be able to call the W-API.
This has made Lazarus unicode enabled long before the compiler helped us with that with it's codepage magic.

The "deprecated" messages is a result of sanitizing the FileUtil and LazFileUtils units, which we did long time ago (IIRC before the release of fpc 3.0).

And now we seem to be in yet anther transition where we can get rid of the UTF8 file functions alltogether in the future.
So, there probably wil be more deprecation going on in this area.

Calling this "f*ck-up" is just spiteful.

Bart

[JuhaManninen]

My answer to the original question is the correct one from the perspective of the given message, except that where I wrote LazUtf8, you are supposed to read LazFileUtils.
If you want to use FileExistsUtf8, you are now supposed to call the one from LazFileUtils.

True, there were 2 separate things: deprecation of function wrappers and the bigger change in Unicode support.
As both changes were related to Unicode they were made around the same time.

[Ondrej Pokorny]

Thaddy likes to spam everything with nonsense comments. Especially FPC bug reports - he comments and disputes everything even if he doesn't try to understand the issue and is wrong in most cases. I am so happy he is not very active on Lazarus mantis.

Well and that you don't say I don't bring any proofs. Just from today:
https://bugs.freepascal.org/view.php?id=31746
https://bugs.freepascal.org/view.php?id=31714