RE: Compile error when using field in a subfield data structure

I think it would be better to just use a different source type and command for 
future free-form RPG.  The free-form apply to all spec (H, F, I, D, C, O) and 
no longer require /Free directive.

Mixing them just doesn't look nice and can easily confuse newbie.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Hans Boldt
Well, there, we're running into the limitations of the I-Spec and 
O-Spec. Back when RPG IV was being designed, a lot of things weren't 
adequately foreseen, and not much effort was put into improving these 
particular specs. (Hindsight is always 20/20, eh?) So now there are 
still lots of places where the traditional syntax drags us down. Do you 
think this issue is important enough to justify new free-form I and O 
specs? ;-)