Skip to main content

OR logic si AND logic - never say never

Mi-am adus aminte de o experienta nefericita pe care am avuto la începutului anului cu operatorii logici.
Era nevoie să fac debug pe un OR logic intre un ulong si un int.
int sursa1;
ulong sursa2;
Init(sursa1,sursa2);
ulong stare=sursa2 | sursa1;
Din pacate nu puteam sa folosesc enum. Era o aplicație vechie, care a fost portata de cineva in C# si era plina de erori de compilare. Nimeni nu cunoștea exact care sunt stariile in care se poate ajunge variabila stare si ce înseamnă fiecare stare.
Prima problema pe care o aveam era ca linia de cod care facea OR logic, codul nu compila deloc din cauza ca cele doua date( sursa1 si sursa2) erau de tipuri diferite. Eroarea pe care o primeam era "Operator | cannot be applied to operands of type int and ulong.". Era normal sa avem aceasta eroare, deoarece sursa2 era strict pozitiva, in comparație cu sursa1 care era o variabila cu semn(+/-).
Nici o problema am zis:
ulong stare= sursa2 | (ulong) sursa1;
Codul a compilat, aveam un warning legat de modul in care se face casting-ul dar am zis ca e okay si am trecut mai departe. Dupa o zi sau doua am ajuns sa rulez aplicatia si surpriza, valoriile pe care le optineam in urma OR logic erau eronate. Obtineam niste valori care nu aveau nici o legatura cu valoriile pe care le asteptam.
Am stat cîteva ore bune pana să îmi dau seama ce se întîmpla. Problema apărea din modul in care se face CAST. Noi vrem să obținem un ulong din int. Dar conversia care se face nu este directa, de la int la ulong, asa cum poate ne-am astepta. Pășii pe care ii face .NET sunt:
int -> long -> ulong
Prima data int este convertit in long iar apoi in ulong. In momentul in care se face conversia la long valoarea pe care noi am asteptao se pierde in totalitate.
Solutia pe care am gasito, desi pare ciudata este:
ulong rezultat = sursa 2 | (ulong)(long) sursa1;
Ciudat nu? Eu zic ca e destul de ciudat. Cand lucrati cu OR logic sau AND logic, incercati sa evitati sa lucrati cu tipuri diferite de date. Recomandarea mea este sa evitati OR logic. Puteți folosii cu succes, enum-ul in acest caz, unde fiecare stare sa aibe o anumita valorea binara(FLAG).
Exemplu:
    [Flags]
enum FileType
{
None = 0x0,
Exe = 0x1,
Zip = 0x2,
Video = 0x4,
Sound = 0x8,
D3 = 0x10
}




Problema era ca rezultatul care era obtinut in urma acestui OR logic nu era cel asteptat.

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP