?
Solved

Delphi 7 difficulties with comments in code

Posted on 2003-11-07
5
Medium Priority
?
1,022 Views
Last Modified: 2007-12-19
L.S,

I try to convert existing Delphi 4 code into Delphi 7 (studio architect version) and I experience very strange behaviour of D7 with respect to the use of comments within the code.

It looks like that D7 does not accept the comments (generates an error "line
too long (more than 1023 characters)". It appears that at some location all comments need to be removed. Not in all cases, strange enough.

The D4 programs to be recompiled contain a lot of table handling code using the BDE, and I have a feeling that this has to do with the error.

Does anybody know why this is and what to do about it (except for stripping all valualbe information from the code) ?


Thanks in advance,
JGMS
0
Comment
Question by:JGMS
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 12

Accepted Solution

by:
andrewjb earned 50 total points
ID: 9703455
Might be worth checking to see whether the lines are correctly terminated i.e. with <CR><LF> and not just a <CR> or just a <LF>.

That's confused the compiler in the past - maybe it doesn't know comments span multiple lines...

Copy/Paste from the PVCS source control tool has done this to me before now..
0
 

Author Comment

by:JGMS
ID: 9704166
The code complies normally in D4. A number of comment containing code compile normally, so I do not expect CR/LF causes.
0
 
LVL 26

Expert Comment

by:EddieShipman
ID: 9705735
Open it in another text editor to ss if the line termination is correct before opening it in Delphi7.
0
 
LVL 1

Expert Comment

by:Chopinke
ID: 9705781
IF you have a cr only or lf only problem, then open your text in WordPad (turn off WordWrap) and save. Wordpad will automatically convert all line ends to cl/lf.
0
 

Author Comment

by:JGMS
ID: 9709784
L.S.

The CR/LF point indeed appeared to be the problem, or perhaps part of the problem.

After opening and saving the code in a text editor, it passed the syntax check without errors but generated a fatal error during compilation: "Internal error L1333". No clue on the internet about this, but fortunately the problem dissapeared after running a number of updates from the Borland site.

Thanks, JGMS
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction Raise your hands if you were as upset with FireMonkey as I was when I discovered that there was no TListview.  I use TListView in almost all of my applications I've written, and I was not going to compromise by resorting to TStringGrid…
In my programming career I have only very rarely run into situations where operator overloading would be of any use in my work.  Normally those situations involved math with either overly large numbers (hundreds of thousands of digits or accuracy re…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment. To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Suggested Courses
Course of the Month10 days, 16 hours left to enroll

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question