Re: JS lib house of cards - you ARE the weakest link!
Source code be it public or proprietary MUST be properly coded IN THE FIRST PLACE !!!
I'm used to an environment where EVERYTHING is considered CRITICAL SYSTEMS CODE usually used in aerospace, weapons and nuclear systems where MILLIONS of people can DIE if it doesn't work or it doesn't error trap properly! We have been FORCED to write proper code for DECADES
now, so it has become second nature.
The basic gist of the matter is MOST CODERS SUCK --- When YOU can write easy-to-understand and WELL-COMMENTED code then GitHub will become usable by the average person:
Copy to a word processor and change the font to Courier New 12 point bold and see
what MY PROPERLY COMMENTED CODE looks like:
Type
// Set generic globally-available integer data types that can be 8, 16, 32, 64 or 128-bits
// in size that DO NOT NEED to be of an application-or-hardware-dependent bit-width.
Signed_Integer_Type = Signed_64_Bit_Integer;
Runtime_Identifier_Type = Signed_Integer_Type
{
*******
Set Basic Record/Object Identification and Owner Identification
Numbers that are unique to the Local-machine and/or local LAN.
*******
}
Procedure Record_Header_Type.Set_Identification_Numbers(
New_Identification_Number,
New_SubIdentification_Number,
New_Owner_Identification_Number : Runtime_Identifier_Type );
Var
Saved_Line_Number_For_Code_Failure : Signed_Integer_Type;
Begin
Try
{
These are basic low-level integer-based identifiers for internal programmer use.
These allow applications to identify specific records and the objects they contain
using a singular major identification number and a minor identification number.
There are allowed to be duplicates of the major identification numbers within
an application but for true differentiation, use the minor more-granular
identification number. The Owner identification number lets applications,
systems and upper-level container object/items determine to whom or what
they belong to and/or are directly controlled by.
The line number definitions allow the internal always-on, realtime debugger
to save a specific local-procedure code location so that the system can fail
gracefully when ID numbers are NOT able to be defined at runtime.
This allows us to find WHICH record property handler is causing
the problem.
}
Saved_Line_Number_For_Code_Failure = LINE_1;
Identification_Number := New_Identification_Number;
Saved_Line_Number_For_Code_Failure = LINE_2;
SubIdentification_Number := New_SubIdentification_Number;
Saved_Line_Number_For_Code_Failure = LINE_3;
Owner_Identification_Number := New_Owner_Identification_Number;
Except
// Upon any low-level error or runtime exception, do nothing else after the
// save error information handler, and immediately exit this Record Field Handler Method.
Set_Global_Error(
ERROR_IS_UNABLE_TO_SAVE_ID_NUMBERS,
'FAILED RECORD METHOD: Set_Identification_Numbers()',
Saved_Line_Number_For_Code_Failure,
Get_Current_Time_and_Date_As_String,
SAVE_TO_LOCAL_LOG_FILE + SEND_ERROR_TO_SERVER )
End;
End;
THIS is how EVERY SINGLE FUNCTION AND PROCEDURE should be written in a properly coded CRITICAL SYSTEMS STYLE of coding!
d
