Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[xboxisfinished]

   Hey guys,

I am intending to make pacman and pacman construction set. The pacman construction set is easy to do and I should have it within a month or two..a full functioning pacman construction set.

The pacman engine is the more...challenging part (I can do it though). Because of the compiler bug for AMOS....I need to be able to use unlimited amount of if statements if it should come a time where my logic requires multiple if statements (not that I want to go trillion if statements either). I was thinking...what if I wrote multiple libraries and then inside those libraries are functions or subroutines that can be called into the main program?

How do I inherit libraries and how do I make my own custom library and finally...how do I add them all into the compiler so that compiler can compiler each file separately than the other?

Thanks in advance. If this can be done..then I can make 80% of my custom chipset games on AMOS that way!

[SamuraiCrow]

Look for the Include command.  It should be able to import external source.

[Hungry Horace]

" need to be able to use unlimited amount of if statements if it should come a time where my logic requires multiple if statements "

This compiler bug is very easly worked around.

The bug is only on numbers of 'ELSE IF' statments, so you have two options:

1)  Use normal IF / ENDIF that only passed on the criteria you want - dont allow ELSE to 'catch' anything you dont want it to.

2) Do your logic checking for this in a GO SUB routine. As above, use IF / ENDIF for the logic test, and then add RETURN inside the passed routine.

e.g.

Code: [Select]

GOSUB DoChecks:
.. normal code here...
END


DoChecks:

IF INPUT=UP AND NORTH_WALL=FALSE : Y=Y-1 : RETURN : ENDIF
IF INPUT=UP AND NORTH_WALL=TRUE : Y=Y : RETURN : ENDIF
IF INPUT=DOWN AND SOUTH_WALL=FALSE : Y=Y-1 : RETURN : ENDIF
IF INPUT=DOWN AND SOUTH_WALL=TRUE : Y=Y : RETURN : ENDIF

RETURN


[xboxisfinished]

" need to be able to use unlimited amount of if statements if it should come a time where my logic requires multiple if statements "

This compiler bug is very easly worked around.

The bug is only on numbers of 'ELSE IF' statments, so you have two options:

1)  Use normal IF / ENDIF that only passed on the criteria you want - dont allow ELSE to 'catch' anything you dont want it to.

2) Do your logic checking for this in a GO SUB routine. As above, use IF / ENDIF for the logic test, and then add RETURN inside the passed routine.

e.g.

Code: [Select]

GOSUB DoChecks:
.. normal code here...
END


DoChecks:

IF INPUT=UP AND NORTH_WALL=FALSE : Y=Y-1 : RETURN : ENDIF
IF INPUT=UP AND NORTH_WALL=TRUE : Y=Y : RETURN : ENDIF
IF INPUT=DOWN AND SOUTH_WALL=FALSE : Y=Y-1 : RETURN : ENDIF
IF INPUT=DOWN AND SOUTH_WALL=TRUE : Y=Y : RETURN : ENDIF

RETURN


YOU ARE SERIOUS? ALL I HAVE TO DO IS MAKE SURE NOT TO USE ELSE IF??! AAAAAAAAAAAAAAAAAAAAAAAAH!!!

I AM MAKING AN ANNOUNCEMENT THAT 100% OF MY CUSTOM CHIPSET GAME PROJECTS WILL BE AMOS EXCLUSIVE! I CAN FINALLY MAKE MY DREAM GENRA OF ADVENTURE/RPG ETC ON MY AMIGA!! With the power of AMAL, build in sprite editor, etc...I HAVE LITERALLY GAME MAKER CONSTRUCTION UNDER MY HANDS AHAHAHAHAHAHAHHAAHHAHAHAHAHAHAHAH!!!!

If the compiler can compile all my projects and the one bug is else if...WHO NEEDS ELSE IF! ELSE IF IS STUPID ANYWAYS! AHAHAHAHAHAHAHA!!!

HECK...I wouldn't even bother fix the bug then..FOCUS ON THE INTERPRETER...ADD FEATURES AND FIX BUGS ON THE INTERPRETER...I wouldn't mind using compiler version 2.0 at year 2030 or 2060 (if I am still alive)!

[Hungry Horace]

yep, i remember having this bug myself on the Bloodwych Editor.... removal of the ELSE IFs solved it completely.

There are, of course, other bugs with the compiler, but i am sure we can help you past them!