Re: Simple Question?

>Now that exists some real world datablade expertise, >perhaps someone could answer a simple question. > >I would like to see how datablades (UDO) enhances my application. > >This hypothetical application(s) deal with a bank. >(Financial Institution.) > >the question: "How will UDO help me better manage my portfolio, (A/LM), >or my Derivitives?" > >For those not familiar with Derivitives, they are merely financial >contracts or >obligations attached to some underlying security. >(SWAPS, CAPS, SWAPTIONS, CMO's, etc ...) > >Or even FXs? > >The idea is to explore how UDO enhances my solutions over non UDO >solutions. > >The reason I ask this is that I am confused as to the *direct* bennifit >of this >technology. > >On a similar note, someone talked about a *video* datablade. Yet from >the post, I don't see >how this is an advantage over other solutions. (Maybe someone could >explain that as well.) > >-Confused Mikey. > > With financial data, the concept of date does not follow the calander date. For instance options generally we commonly refer to March options, but what we really mean are the options that expire on the friday of the third week of March. Also in studying the life of that option, we are not so much concerned about the number of days until the expiration date, but the number of trading days. We could have a whole series of functions to calculate these differences, but that would require the programmer to constantly be aware to call the funtions. It would be much easier to simply state TRADING_DAYS = EXPIRATION_DATE - TODAY. By defining expiration_date as a type, this could automatically happen. In reality, we have always done "objects". The system really only knows about ones and zeros. For instance, a date data type is nothing more than an integer. However, any reference to that date type causes routines to be invoked which invoke that date type differently than a normal integer type. All that object definition does is to enable the programmer/user to expand the built-in data types with new data types that reflect the actual use of that datum. Madison Pruet