PSPad unicode 4.5.8 (2485) English

pspad:

I am looking on your example. It really means you can have strict Cobol with code ending on column 71 and strings in this source can be longer 71 column?
I don't know Cobol, can you confirm it?
If this rule isn't valid, go to settings / Highlighter settings / Specification tab and increase size of end of code.

If end of code is set to 71 column, all behind this column is ignored.

You have two strict formats:

1. free-form reference format
column 7 is for controls, coding parts start at column 8, last column for the coding parts is implementor-specific [normally column 72 (should be the standard setting) is the last one which is not ignored]. In this format you can start a string, don't add the string end on this line, starting the next line in column 7 with - and just go on with the string (needs a start on each line, string end only in the last one). The sample disppar.cob I've sent you highlights this, together with the missing of string endings in the column you can set via highlighter settings -> specification (I've set this to 72 here).
It has both inline comments *> and comment lines via * in column 7

2. fixed-form reference format
without any areas at all, only inline comments *>, no comment lines - see sample colors.cbl

I think the best would be to split both reference formats in two highlighters, not in one. The workaround is to switch the specification settings to 7/8/72 <-> 0/1/255 (while the inline-comments don't work with this setting), depending on the reference-format currently in use.

If there's anything unclear: just ask, I think we will fix it this this time (you the program while I help with the source and explanations).

Simon

Correction: *> currently doesn't work as inline comment, no matter how the settings are.

for free format set sections to 0,0,255
*> as inline comments works for me.

In free format anywhere, in strict format when it start in section B

pspad:

for free format set sections to 0,0,255
*> as inline comments works for me.

In free format anywhere, in strict format when it start in section B

Free Format with 0,0,255 works fine (I suggest to add a label in the specification telling the standards for fixed-form and free-form reference format - or even better: adding two buttons for easily set the one or the other (own entries or changes in the set cols can be done manually).
And another suggestion: Set OK as the default button, leading to ENTER leavin the dialoge (currently [ALT]+[O] is needed).

*> works for me now, too. I was just confused by a bug: the strings are not shown correctly on load.

Steps to reproduce:
- open colors.cbl, close all other files
- set the specification to 0,0,255
- close and reopen PSPad
- according to the string highligter a string is opened in line 20 and nowhere closed (this only gets solved if you add a space in this line and remove it afterwards)

Simon

I will add buttons to quickly set default and strict syntax.

pspad:

I will add buttons to quickly set default and strict syntax.

Sounds good, I guess you talked about "fixed-form reference format" (1,7,72) and "free-form reference format" (0,0,255)?

Simon

yes

After update PSPad from 2471, some FTP return an error:
'0-0-0 0:0:0,0'' is not a valid date and time.

Full error log:
Exception description:

''0-0-0 0:0:0,0'' is not a valid date and time.

Exception class: EConvertError
Exception address:
----------------------------------------------------------------------------------------------------
Stack list, generated 2014-09-08 18:17:30


Please do not post such list to the forum.
 
Send them to Jan by mail (see Help > About)
 
Thank you.


----------------------------------------------------------------------------------------------------
Program : C:\Users\elnino\Dropbox\Common\PSPad editor NEW\PSPad.exe 4.5.8 (2485)
System : Windows 7 Professional x64, Version: 6.1, Build: 1DB1, Service Pack 1
Processor: Intel, Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz, 3600 MHz MMX
Display : 1680x1050 pixels, 32 bpp
----------------------------------------------------------------------------------------------------
Active Controls Hierarchy:
TPSSynEdit ""
TfChildEdit ""
----------------------------------------------------------------------------------------------------


Edited 1 time(s). Last edit at 2014-09-09 14:44 by Stefan.

The COBOL syntax is OK! I had to change the last col to 72 in the highlighter settings ; by default it was 71.
Thx!

MadCompie:

The COBOL syntax is OK! I had to change the last col to 72 in the highlighter settings ; by default it was 71.
Thx!

What is the correct default value for strict syntax? 71 or 72?