Project

General

Profile

Bug #7836

explicit buffer scope when defined at external program and used in an internal entry

Added by Constantin Asofiei 7 months ago. Updated 7 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:

History

#1 Updated by Constantin Asofiei 7 months ago

This is an existing issue:

.\a.p                                09/20/2023 20:57:12   PROGRESS(R) Page 1   

{} Line Blk
-- ---- ---
      1     
      2     def buffer bb for book.
      3     
      4     procedure proc1.
      5   1   for each bb:
      6   1      message bb.isbn.
      7       end.
      8     end.
      9     
.\a.p                                09/20/2023 20:57:12   PROGRESS(R) Page 2   

     File Name       Line Blk. Type   Tran            Blk. Label            
-------------------- ---- ----------- ---- --------------------------------
.\a.p                  4 Procedure   No   Procedure proc1                  
.\a.p                  5 For         No                                    
.\a.p                  0 Procedure   No                                    
    Buffers: p2j_test.bb

In FWD will emit the bb scope at the FOR EACH block in proc1 instead of the external program.

The same happens for a temp-table explicit buffer.

It seems that in OpenEdge, explicit buffers defined at the root level must be scoped at the root level if they are used in an internal entry. But the test needs to be expanded to find the extent for this.

Also available in: Atom PDF