You are not logged in. You can browse in the PowerBASIC Community, but you must click Login (top right) before you can post. If this is your first visit, check out the FAQ or Sign Up.
I've never had any problems putting DECLARE statements or equates in the source preceding the procedure in which they are referenced; that is, I can have
Code:
DECLARE SUB xxxx
DECLARE FUNCTION....
%One = 1
SUB Foo...
END SUB
FUNCTION Bar..
END FUNCTION
DECLARE SUB baz
%THREE = 3
SUB Baz..
END SUB
Near as I can tell, anything goes as long as you follow the cardinal rule: A DECLARE for a procedure or "define" for an equate must physically precede its use in code.
While merging the code for several small dlls into one dll, I noticed that PB requires that you put metastatements before any "regular statements". Am I correct? And are there any other rules for the order of code, such as the position of DECLAREs, equates, etc.? I didn't see anything in the manual or help file about this.
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, and to analyze site activity. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Leave a comment: