SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Y2K (Year 2000) Stocks: An Investment Discussion -- Ignore unavailable to you. Want to Upgrade?


To: Hoatzin who wrote (7162)10/27/1997 10:30:00 AM
From: TEDennis  Read Replies (2) | Respond to of 13949
 
Kevin: Re: cost per line of object code ...

I snickered about that comment when I read it, too. Obviously, the writer was interpreting some notes given to him by somebody, or they were notes taken in a verbal interview. Either the writer put his own words to his interpretation, or whoever fed the info to him was slightly less than technically proficient (was that polite enough?).

Here's my guess ... the solution is billed at a per-line-of-source-code rate, similar to all the other solutions. Or, it could be billed at a per object code 'patch' rate, in which case I think it will be more expensive than initial reports. There are lots of areas that need to be intercepted for this solution to make any sense.

I doubt it would be charged by the K-byte of object size because there are some process intensive object modules that have a very small percentage of code that is date dependent. And, if you have a program that has a large static table of control information, you'd be paying for something that would never need to be fixed.

Which reminds me ... if he's only looking at object code, how can he determine the difference between instructions and data? That's easy for the major compiler languages (COBOL, PL/I, etc.), but what about Assembler code? Having been involved with a disassembler in the past, I know that it's darned near impossible to determine in an ALC module. And, what about those ALC modules that are self-modifying? Hmmmmm ...

Regards,

TED



To: Hoatzin who wrote (7162)10/27/1997 6:02:00 PM
From: tom rusnak  Read Replies (1) | Respond to of 13949
 
Kevin RE: lines of code,

In the short time since Y2k has been around, industry standard for charging seems to be based on lines of code. Even though you go into a client site with a 'sourceless' solution, they seem more comfortable talking about lines of code, and it also gives them a basis for comparing prices amongst solution providers.

tom