- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Compiling (using CVF 6.6B) a rather large source module (which had compiled fine recently under a previous version of CVF) now causes the following warnings/errors:
Warning: A jump into a block from outside the block has occurred.
Error: An ENTRY statement must not appear within an executable construct (R1223.2)
Error: An unterminated block exists.
We don't think that the source code has changed. Upon inspection of the code, we believe that the warnings and errors are spurious... We are not jumping into a block from outside the block. And we don't really understand the meaning of the second message: That an ENTRY statement must not appear within an executable construct. What is the meaning of "executable construct"?
Thanks!
Warning: A jump into a block from outside the block has occurred.
Error: An ENTRY statement must not appear within an executable construct (R1223.2)
Error: An unterminated block exists.
We don't think that the source code has changed. Upon inspection of the code, we believe that the warnings and errors are spurious... We are not jumping into a block from outside the block. And we don't really understand the meaning of the second message: That an ENTRY statement must not appear within an executable construct. What is the meaning of "executable construct"?
Thanks!
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In this context, "executable construct" would mean a CASE, DO, IF or WHERE block.
We continue to improve the compiler's detection of errors, and it may be that your program is really invalid - or it could be we made a mistake. If you think the latter, send a compilable source (smallest you can manage, please) to vf-support@compaq.com and it will be looked at.
Steve
We continue to improve the compiler's detection of errors, and it may be that your program is really invalid - or it could be we made a mistake. If you think the latter, send a compilable source (smallest you can manage, please) to vf-support@compaq.com and it will be looked at.
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Steve,
Thanks for the link to the repaired compiler. It solved the problem. And thanks too for the quick response!
Thanks for the link to the repaired compiler. It solved the problem. And thanks too for the quick response!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Oh, that was you! Yeah, that bug you encountered was certainly a strange one.... Glad to hear that the updated compiler fixed it (I figured it would, since I knew the bug had been fixed.)
Steve
Steve
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page