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

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 …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…