@ -119,10 +119,10 @@ Generally it will depend on the particular piece of code and would be determined
### 4. File encoding and line endings.###
### 4. File encoding and line endings.###
UTF-8 and Unix-like line ending (LF). Unless some platform speficic files need other encodings/line endings.
UTF-8 and Unix-like line ending (LF). Unless some platform specific files need other encodings/line endings.
### 5. Initialization lists.###
### 5. Initialization lists.###
Initialization lists should be vertical. This will allow for more easily readable diffs. The inilization colon should be indented and in its own line along with first argument. The rest of the arguments should be indented too and have the comma prepended.
Initialization lists should be vertical. This will allow for more easily readable diffs. The initialization colon should be indented and in its own line along with first argument. The rest of the arguments should be indented too and have the comma prepended.
"([a-zA-Z0-9\\?%=&/_\\.:#;-]+)"// everything to 1st non-URI char, must be at least one char after the previous dot (cannot use ".*" because it can be too greedy)
"([a-zA-Z0-9\\?%=&/_\\.:#;-]+)"// everything to 1st non-URI char, must be at least one char after the previous dot (cannot use ".*" because it can be too greedy)
")"
")"
"|"
"|"
"("// case 2b no scheme, no TLD, must have at least 2 aphanum strings plus uncommon TLD string --> del.icio.us
"("// case 2b no scheme, no TLD, must have at least 2 alphanum strings plus uncommon TLD string --> del.icio.us
"([a-zA-Z0-9_-]+\\.) {2,}"//2 or more domainpart. --> del.icio.
"([a-zA-Z0-9_-]+\\.) {2,}"//2 or more domainpart. --> del.icio.
"[a-zA-Z]{2,}"//one ab (2 char or longer) --> us
"[a-zA-Z]{2,}"//one ab (2 char or longer) --> us
"([a-zA-Z0-9\\?%=&/_\\.:#;-]*)"// everything to 1st non-URI char, maybe nothing in case of del.icio.us/path
"([a-zA-Z0-9\\?%=&/_\\.:#;-]*)"// everything to 1st non-URI char, maybe nothing in case of del.icio.us/path