Skip to main content

Ordonare in sens invers - generic

Era nevoie sa implementez un mecanism de ordonare. Deoarece existau mai multe tipuri de ordonare pe acelasi obiect, am ales sa folosesc IComparer.
IComparer este un mecanism de comparare extern. Implementarea functiei care face compararea nu este in interiorul obiectului, asa cum este in cazul IComparable. Se foloseste de obicei cand modul in care se face comparatie nu este naturala.
Cand se implementeaza interfata IComparer, este nevoie sa implementam metoda int Compare(T obj1,T obj2), care returneaza o valorea
  • pozitiva daca obj1 > obj2;
  • negativa daca obj1 <>
  • zero daca obj1 = obj2;
Pana aici nu apare nici o problema. Dar daca avem nevoie sa putem face si o ordonare inversa( reverse), apar probleme. Nu neaparat la modul de implementare, putem foarte usor sa ne folosim de operatorul de negare !, ci la modul in care facem implementarea. Am cautat un mecanism de ordonare in sens invers, care sa fie cat mai generic.
Solutia pe care o propun este urmatoarea:
public class ComparerReverse<T>: IComparer<T>
where T: class
{
//Stocam implementarea deja existenta.
private readonly IComparer<T> _comparer;

public ComparerReverse(IComparer<T> comparer)
{
_comparer = comparer;
}

public int Compare(T obj1,T obj2)
{
//Apelam Compare de la implementarea de baza, cu cei doi parametri inversati.
return _comparer.Compare(obj2,obj1);
}
}
Prin solutia propusa nu mai este nevoie sa folosim operatorul de negare ! si putem sa folosim aceiasi apelare pentru ambele sensuri de ordonare:
...
IComparer<T> comparerUsa=crescator
?new UsaComparare()
:new ComparerReverse(new UsaComparare());
...
Urmatorul pas este sa cream un extension method care sa faca ordonarea in sens invers:
public static class ComparerReverseExtension
{
public static IComparer<T> Reverse<T>(this IComparer<T> comparer)
{
return new ComparerReverse<T>(comparer);
}
}
Folosind acest extension method putem sa inversam modul in care se face comparatia apeland Reverse() direct la IComparer pe care vrem sa il folosim pentru a face ordonarea in sens invers.

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(

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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too