Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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 : Discuss Year 2000 Issues -- Ignore unavailable to you. Want to Upgrade?

To: John Mansfield who wrote (657)	12/11/1997 2:11:00 PM
From: John Mansfield	Read Replies (1) \| Respond to of 9818

Y2K-Europe. No help from India for German banks? 'Y2K Discussion on the board of the CDU - the German party of Chancellor Kohl: Posting: cdu.de Thread: cdu.de A German programmer: 'A large german bank wanted to remediate their programs in India. There was a slight problem, however: the source code was in English; but most of the programmers had written their comments in German. Now try to understand a program when you can not understand the comments.' 'Eine grosse Deutsche Bank wollte z.B. ihre Programme in Indien ueberarbeiten lassen. Gab allerdings ein kleines Problem: Der Source-Code ist zwar in Englisch, aber die meisten Progs haben ihre Kommentare in Deutsch geschrieben. Jetzt versuchen Sie sich mal in ein Programm einzulesen, ohne das Sie die Kommentare verstehen.' John

To: John Mansfield who wrote (657)	12/11/1997 2:18:00 PM
From: John Mansfield	Read Replies (1) \| Respond to of 9818

Y2K-Java - Stop the rot - why Y2K must appear in PC magazines I found yet another sample of non compliant code that is written today. This rotting has to stop. the only way is by publishing in the pc/java/c++/... magazines. This is from the SIM board; excellent source of information! Thanks to David Hall. John ------------------------------------------------ 14. Author: David C. Hall ( dhall ) Date: Oct. 31 3:51 PM 1997 Interesting acticle in the October 27, 1997 issue of WebWeek. The one entitled Dr. Website: Sharp Readers Point to Potential Problems with Last-Modified Code. The Dr. Website column of Sept 29, 1997 featured some JAVASCRIPT code for showing the last-modified date of a document. The code they created had a Year 2000 problem and a couple of readers pointed that out. The code ran like this: document.write("FONT SIZE=4 FACE=\"ARIAL\">&ltB&gtUpdated "+mon + " " ", " + "19"+year + " at " +hour +":" +min + "</FONT>"); Basically ANY code and/or application can be made non-Yr2K compliant if the programmer does not break old habits, habits that are ingrained in our training courses, our programming books, our experiences, etc. Just becasue you make your enterprise Yr2K compliant is no reason to sit back and take a deep breath. Establish Quality Control procedures and policies to minimize such bad programming practices. Dave Hall