declare variable - bug or poor design?

[Joe Chasan]

consider the following line of code:
declare local test_field(len(1),edit(1))

then you code some routines around test_field and figured you have the 
system beat, you won't have to change dummy field length/type if field
#1 changes at all.  great for reusable code, libraries, etc, or so I 
thought.

today i changed field length.

in define processing, if you press <F6><L> it correctly reports the
current field length/type of test_field

BUT - if you do not save the processing table and retokenize, rclerk
still has the old length/type (dclerk works).  

If this construct is not adjusted at runtime (even with quickstart),
what is the point of this "feature"?

Bug?  Poor design?

(5.6.11/sco - reproducable on sco5 and sco6)

--
-Joe Chasan-                           Magnatech Business Systems, Inc.
joe - at - magnatechonline -dot- com   Hicksville, NY - USA
http://www.MagnatechOnline.com         Tel.(516) 931-4444/Fax.(516) 931-1264