Skip to main content

How NOT to use AS keyword

Mai mult ca sigur ati folosit pana acuma "as". Prin intermediul sau se poate face cast unui obiect la un tip dat, iar in cazul in care cast-ul nu se poate face, valoarea returnata este null.
BaseItem item = val as BaseItem;    // returneaza null daca nu poate sa faca conversia
BaseItem item = (BaseItem) val; // arunca exceptie daca nu poate sa faca conversia
Despre "as" am mai discutat in acest post: http://vunvulearadu.blogspot.com/search/label/C%23%20AS%20Keyword%20Cast%20speed%20performance
Mai jos o sa va prezint un mod mai ciudat de a folosii keyword-ul "as". A fost folosit pentru a detecta daca un element este de un anumit. Iata cum a fost folosit:
BaseItem item;
...
if ( item as CarItem != null )
{
...
}
else if ( item as BookItem != null )
{
...
}
else if ( item as ClassItem != null )
{
...
}
Ce mi s-a parut interesant este cum a fost folosit "as". In locul sau se poate folosii fara probleme "is". Acesta o sa returneze true daca un obiect se poate converti la tipul dat. Codul de mai sus se poate rescrie in felul urmtor:
BaseItem item;
...
if ( item is CarItem )
{
...
}
else if ( item is BookItem )
{
...
}
else if ( item is ClassItem )
{
...
}
Codul arata ceva mai bine, dar inca ceva ce nu pare okay. Ca sa scapam de acest lant de IF-uri putem sa ne declaram in BaseItem o metoda virtuala sau abstracta la care sa facem override in clasele noastre( CarItem, BookItem,CLassItem). Prin acest mod am avea un singur apel la o metoda, care pentru fiecare din clasele noastre poate sa execute codul dorit:
abstract  class BaseItem
{
public abstract void DoAction();
}
public class CarItem : BaseItem
{
public override void DoAction()
{
...
}
}
... pentru fiecare din clasele noastre ...
Iar insiruirea de IF-uri pe care era mai sus devine:
item.DoAction();

Enjoy!

Comments

  1. Cel ce a scris codul ala, n-o fi auzit de 'is' sau polimorfism, se mai intampla.. :)

    ReplyDelete
  2. Si ce faci daca nu ai control asupra clasei respective? Primesti un object si in functie de tipul lui real trebuie sa procedezi intr-un fel? Ai posibilitatea Double Dispatch, care este un pattern consacrat, dar de asemenea (in .NET 4.0) la ceva de genul:
    myMethod((dynamic)obj);
    ca apoi sa implementezi myMethod pentru diferite tipuri. "Defaultul" fiind myMethod(object obj) { throw something }

    ReplyDelete
  3. Belele si mai mari poti avea cu "as" cand nu se face verificarea de null a rezultatului si se paseaza acest rezultat unei alte metode si care il mai paseaza altei metode si intr-un final crapa cu NullReferenceException dar nu unde a esuat conversia ci zece kilometri mai departe, ingreunand depanarea.

    Nu ma intrebati cum stiu asta...

    ReplyDelete
    Replies
    1. Odata si odata tot apare un NULL, daca nu faci o verificare dupa ce faci conversia sau cand referi variabila obtinuta cu "as". Nu te intreb de unde stii, presupun ca ai avut parte de un debug destul de naspa :-(

      Delete

Post a Comment

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