Author | Topic: Problems with Remarks/Comments | |
---|---|---|
Andreas Gehrs-Pahl | Problems with Remarks/Comments on Wed, 24 Dec 2003 01:44:37 -0500 The Editor can't identify any single line remarks that start with a "*" unless the "*" is the first character of the line. The editor should ignore any white space characters in front of the "*", as the preprocessor and compiler do the same. Also, the Editor does not recognize the (old) "&&" inline remark identifier, either! I could theoretically change all "&&" in all my source code files to "//", but the indentation of "*" remarks makes the source code more readable, and I do not want to miss that feature! Can I fix or modify this shortcoming by myself? If not, can this be fixed before the final release of VX? -- Andreas --- --- Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net 415 Gute Street or: Andreas@DDPSoftware.com Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net --- --- | |
Andreas Gehrs-Pahl | Re: Problems with Remarks/Comments on Wed, 24 Dec 2003 02:33:36 -0500 I wrote: >The Editor can't identify any single line remarks that start with a "*" >unless the "*" is the first character of the line. The editor should ignore >any white space characters in front of the "*", as the preprocessor and >compiler do the same. >Also, the Editor does not recognize the (old) "&&" inline remark identifier, >either! This also wrecks havoc with the Project Manager/Code Explorer, that can't display or jump to the appropriate Functions, Procedures, and Methods, if there is some confusing text inside those (not recognized) remarks! This MUST be fixed! I simply can't change all of my source code to comply with those VX quirks! -- Andreas --- --- Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net 415 Gute Street or: Andreas@DDPSoftware.com Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net --- --- | |
Andreas Herdt | Re: Problems with Remarks/Comments on Wed, 24 Dec 2003 12:39:09 +0100 Hi Andreas, I can not give any promisses for the inline comment of "&&" and "NOTE" since they are labeled as deprecated. We have to investigate in this next year. BUT: can you clearify what problems you have with the * comment ? At my place any line started with * is greyed? Regards Andreas Herdt Andreas Gehrs-Pahl wrote: > The Editor can't identify any single line remarks that start with a "*" > unless the "*" is the first character of the line. The editor should > ignore any white space characters in front of the "*", as the preprocessor > and compiler do the same. > > Also, the Editor does not recognize the (old) "&&" inline remark > identifier, either! > > I could theoretically change all "&&" in all my source code files to "//", > but the indentation of "*" remarks makes the source code more readable, > and I do not want to miss that feature! > > Can I fix or modify this shortcoming by myself? If not, can this be fixed > before the final release of VX? > > -- Andreas > > --- > --- > Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net > 415 Gute Street or: Andreas@DDPSoftware.com > Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net > Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net > --- > --- ////////////////////////////////////////////////////////////////// // // Alaska Research & Development // Homepage: www.alaska-research.com // Newsgroup: nntp://news.alaska-Software.net // ////////////////////////////////////////////////////////////////// | |
Andreas Gehrs-Pahl | Re: Problems with Remarks/Comments on Wed, 24 Dec 2003 08:36:24 -0500 Andreas, >I can not give any promisses for the inline comment of "&&" and "NOTE" >since they are labeled as deprecated. We have to investigate in this >next year. If the "&&" are not recognized anymore, I can probably live with this, and convert all the existing code from "&&" to "//". It would help, if there would be an easy way to replace the character sequence: TAB + "&&" + SPACE to the new sequence: TAB + "//" + SPACE as this would make sure that only my comments are changed, and not also literals where "&&" might be used. I suppose the Regular Expression option should allow me to do this, but I am pretty weak on how to use that! >BUT: can you clearify what problems you have with the * comment ? >At my place any line started with * is greyed? I often have TABs in front of comments as in this example: Function Test(cVal) LOCAL cText := "XXX" do case ******************************* * Call Method for Testing "A" * ******************************* case cVal == "A" cText := SomeCode() ********************************* * Call Function for Testing "B" * ********************************* case cVal == "B" cText := SomeOtherCode() endcase return In the above example, the six remarked lines are not grayed out, and the words "Method" and "Function" in those remarks create problems for the Project Manager and Code Explorer. If you have SPACEs in front of the "*" instead of TABs, the lines are grayed out as expected! So this is only a problem with leading TAB characters, as Mike Evans also pointed out! -- Andreas --- --- Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net 415 Gute Street or: Andreas@DDPSoftware.com Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net --- --- | |
Andreas Herdt | Re: Problems with Remarks/Comments on Wed, 24 Dec 2003 14:45:53 +0100 Problem identified: The problem is the tab character. (Space)* This works ok and the comment is recognised (Space)* By the editor (Tab)* This is the error. Comment is not recognized. Workaround: o Close prg file o Menu: Tools->Editor Options -> Editor Tabpage o uncheck: Use tab character o Reopen Prg. o Now the * comments are recognized by the editor. Attention: I have just recognized another odditie: I assume you have used a tab stop of 3 in your previous editor. I have used the same setting in vx and reopened the file with "use tab character" unchecked. This is my result: Function Test(cVal) LOCAL cText := "XXX" do case ******************************* * Call Method for Testing "A" * ******************************* case cVal == "A" cText := SomeCode() ********************************* * Call Function for Testing "B" * ********************************* case cVal == "B" cText := SomeOtherCode() endcase return This means that vx does not use the tab width that are entered in the editor tab. It falls back to a tab with of 8 characters. This is obviously a bug and must be fixed as soon as possible. I hope this does not make you stop your investigation into vx since then I am forced to drive to Eschborn and fix this Regards Andreas Herdt ////////////////////////////////////////////////////////////////// Alaska Research & Development Homepage: www.alaska-research.com Newsgroup: nntp://news.alaska-Software.net //////////////////////////////////////////////////////////////////Andreas Gehrs-Pahl wrote: > Andreas, > >>I can not give any promisses for the inline comment of "&&" and "NOTE" >>since they are labeled as deprecated. We have to investigate in this >>next year. > > If the "&&" are not recognized anymore, I can probably live with this, and > convert all the existing code from "&&" to "//". It would help, if there > would be an easy way to replace the character sequence: > > TAB + "&&" + SPACE > > to the new sequence: > > TAB + "//" + SPACE > > as this would make sure that only my comments are changed, and not also > literals where "&&" might be used. I suppose the Regular Expression option > should allow me to do this, but I am pretty weak on how to use that! > >>BUT: can you clearify what problems you have with the * comment ? >>At my place any line started with * is greyed? > > I often have TABs in front of comments as in this example: > > Function Test(cVal) > LOCAL cText := "XXX" > do case > ******************************* > * Call Method for Testing "A" * > ******************************* > case cVal == "A" > cText := SomeCode() > > ********************************* > * Call Function for Testing "B" * > ********************************* > case cVal == "B" > cText := SomeOtherCode() > endcase > return > > In the above example, the six remarked lines are not grayed out, and the > words "Method" and "Function" in those remarks create problems for the > Project Manager and Code Explorer. > > If you have SPACEs in front of the "*" instead of TABs, the lines are > grayed out as expected! So this is only a problem with leading TAB > characters, as Mike Evans also pointed out! > > -- Andreas > > --- > --- > Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net > 415 Gute Street or: Andreas@DDPSoftware.com > Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net > Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net > --- > --- | |
Mike Evans | Re: Problems with Remarks/Comments on Wed, 24 Dec 2003 15:04:05 +0200 Andreas I don't have any problem with "*" even if it's not first character in the line (spaces before) Regards Mike Evans "Andreas Gehrs-Pahl" <Andreas@DDPSoftware.com> wrote in message news:d1akbz4ki71b.1ia8z3fnkns7.dlg@40tude.net... > The Editor can't identify any single line remarks that start with a "*" > unless the "*" is the first character of the line. The editor should ignore > any white space characters in front of the "*", as the preprocessor and > compiler do the same. > > Also, the Editor does not recognize the (old) "&&" inline remark identifier, > either! > > I could theoretically change all "&&" in all my source code files to "//", > but the indentation of "*" remarks makes the source code more readable, and > I do not want to miss that feature! > > Can I fix or modify this shortcoming by myself? If not, can this be fixed > before the final release of VX? > > -- Andreas > > --- --- > Andreas Gehrs-Pahl E-Mail: GPahl@CharterMI.net > 415 Gute Street or: Andreas@DDPSoftware.com > Owosso, MI 48867-4410 or: Andreas@Aerospace-History.net > Tel: (989) 723-9927 Web Site: http://www.Aerospace-History.net > --- --- |