Bugs on WINMD, who can clarify ?

[DelphiUdIT 248]

Hello, today this comment (the bottom in the figure) appears in the QP (I omitt the name of the annotator)

 

 

Someone, may be the same who post this, can clariry what means? I use WINMD and have never found any bugs since.

But I'm worried that there is something latent or hidden that I am unaware of.

 

Thanks.

 

 

Edited June 23 by DelphiUdIT

[pcoder 5]

Delphi winmd is not available to me (latest CE user), so I don't know,
but I recommend to compare it with other winmd Pascal providers.

[DelphiUdIT 248]

1 hour ago, pcoder said:

Delphi winmd is not available to me (latest CE user), so I don't know,
but I recommend to compare it with other winmd Pascal providers.

I already have this (old version), but it cannot be compared with the one provided by Embarcadero. They have totally different "constructs" and therefore the comparison is practically impossible.

EDIT: I mean massive comparison. you have to test every single function.

 

The Embarcadero one however reports help data such as the link to the Microsoft page for each single function and other info.

 

example (Emb.):

///<summary>Documentation: https://docs.microsoft.com/windows/win32/api/winnt/nf-winnt-rtlinterlockedflushslist</summary>
///<remarks>
///<para>Supported since: <i>windows5.1.2600</i></para>
///</remarks>
function RtlInterlockedFlushSList(var ListHead: SLIST_HEADER): PSLIST_ENTRY; stdcall;
{$EXTERNALSYM RtlInterlockedFlushSList}

example (Other);

function RtlInterlockedFlushSList(var ListHead: SLIST_HEADER): PSLIST_ENTRY; stdcall; external 'ntdll.dll' name 'RtlInterlockedFlushSList'; {windows5.1.2600}

 

Thanks anyway for the update.

Edited June 23 by DelphiUdIT

[himitsu 3]

Source: https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-1577

 

https://quality.embarcadero.com/browse/RSP-44096
https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-1754
https://www.delphipraxis.net/214473-warnung-vor-winmd.html

......................

Edited June 23 by himitsu

[DelphiUdIT 248]

53 minutes ago, himitsu said:

https://quality.embarcadero.com/browse/RSP-44096
https://embt.atlassian.net/servicedesk/customer/portal/1/RSS-1754
https://www.delphipraxis.net/214473-warnung-vor-winmd.html

......................

Thanks, I have to check if something is wrong ... even if apparently everything is working (but I don't use the reported units ... at least ...)  .

 

P.S.: I had already changed the reference from "Win32Api" to "WinApi.Windows" in the WINMD units I use and deleted the Win32Api unit .... maybe that's why I never had problems.

 

The alternative

might be better ...

 

@himitsu, yes the word "oggi" means "today". That is the screenshoot from the QP in my language.

 

Edited June 23 by DelphiUdIT

[FredS 140]

7 hours ago, DelphiUdIT said:

I use WINMD and have never found any bugs since.

But I'm worried that there is something latent or hidden that I am unaware of.

I once sent out an app after a Delphi update and the new GetAce declaration broke it.. they left it that way for years..

The funny part is that others have run into GetAce issues and where told to switch to WinMD 🙂

 

RSP-44096 was my second attempt to try a newer version of WinMD. Other issues from the prior one have died in the old system.

Anyhow, if you claim to build the API using the M$ supplied db and I can't trust just one single function then I have to assume there are more hidden issues..