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

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Run native .NET application in Docker (.NET Framework 4.6.2)

Scope
The main scope of this post is to see how we can run a legacy application written in .NET Framework in Docker.

Context
First of all, let’s define what is a legacy application in our context. By a legacy application we understand an application that runs .NET Framework 3.5 or higher in a production environment where we don’t have any more the people or documentation that would help us to understand what is happening behind the scene.
In this scenarios, you might want to migrate the current solution from a standard environment to Docker. There are many advantages for such a migration, like:

Continuous DeploymentTestingIsolationSecurity at container levelVersioning ControlEnvironment Standardization
Until now, we didn’t had the possibility to run a .NET application in Docker. With .NET Core, there was support for .NET Core in Docker, but migration from a full .NET framework to .NET Core can be costly and even impossible. Not only because of lack of features, but also because once you…