This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Show posts MenuQuote from: Pumaman on Thu 18/11/2004 19:15:19I can understand that people would find the lower of the two more legible - however it does require that the coder looks up the exact syntax of the possible parameter values every time (especially since most functions use different parameters). So I would really appreciate a 0/1 feature. Maybe using something equivalent to an 'enum' would be the answer? C++ would give a warning like 'conversion from int to enum'.QuoteNo, they are #defined to various different numerical values. This is because people tend to get the parameters mixed up where there is more than one TRUE/FALSE parameter. It also makes the script more readable:
And am I correct to assume that ANYWHERE and the other stuff are actually #defined to boolean values? Because personally, I prefer using 1 and 0 (or TRUE and FALSE) to lengthy text strings.
character[EGO].Animate(3, 5, 1, 1, 0);
vs
character[EGO].Animate(3, 5, 1, BACKWARDS, IN_BACKGROUND);
SetObjectView (0, THE_VIEW_YOU_JUST_CREATED);
AnimateObject (0, 0, 5, 1);
Open Close Read
Push Pull Give
What_is Walk_to Pick_up
Turn_on Turn_off Fix
Unlock Use New_Kid
By continuing to use this site you agree to the use of cookies. Please visit this page to see exactly how we use these.
Page created in 0.125 seconds with 16 queries.