No dream.
Cyclic imports were only the reason sushim wanted a change to import.
Im sujesting that even though we dont want cyclic imports we still want a change in the import/include super/superstrict
Specificaly that the compiler shouldnt throw an error when it finds a "Second" strict/superstrict as long as it wouldnt requires a change in the strict setting. (ie if all your includes have the same strict setting at the top)
I agree totaly about not including things from each other, unless very strong compiler directives are used. (But even then I would probably just use "prototypes". Hummm. Does BMax have prototypes?)
But the basic problem of the two types of "Insert", that which Sushim was posting about, is that some people spend ages reming superstrict in and out.
Cyclic imports were only the reason sushim wanted a change to import.
Im sujesting that even though we dont want cyclic imports we still want a change in the import/include super/superstrict
Specificaly that the compiler shouldnt throw an error when it finds a "Second" strict/superstrict as long as it wouldnt requires a change in the strict setting. (ie if all your includes have the same strict setting at the top)
I agree totaly about not including things from each other, unless very strong compiler directives are used. (But even then I would probably just use "prototypes". Hummm. Does BMax have prototypes?)
But the basic problem of the two types of "Insert", that which Sushim was posting about, is that some people spend ages reming superstrict in and out.