-=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- (c) WidthPadding Industries 1987 ||0 -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=- -=+=-
Socoder -> Blitz -> blitzcc.exe

Posted : Wednesday, 24 November 2010, 00:56 - Mark Unread
Tikihead
Does anyone else occasionally have trouble with Blitz compiling or stepping through a program? Lately it's been treating these two pieces of code differently and just completely janking up the first (preferable) one:

(Pop() returns an integer)

Worked fine up until today


Works, but not preferable


|edit| I haven't been on here much lately; nice site improvements Jay |edit|
Posted : Wednesday, 24 November 2010, 01:16 - Mark Unread
JL235
One thing I noticed with BB is that it uses a very odd order for evaluating parameters. Most languages evaluate parameters either right to left or left to right.

I can't remember the exact order but with BB it's done right to left but will skip some of them and then jump back to evaluate them later. It doesn't call them all in order.

My overall point is that you should never expect the parameters to always be evaluated in a specific order! (This is also true to all programming langauges, not just BB).

-=-=-
PlayMyCode.com - build and play in your browser, Blog, Twitter.
Posted : Wednesday, 24 November 2010, 09:14 - Mark Unread
Scherererer
There are some languages (like Haskell) that don't even evaluate the parameters until they're needed in the function call!

-=-=-
YouTube Twitter
Computer Science Series: Logic (pt1) (part 2) (part 3) 2's Complement Mathematics: Basic Differential Calculus
Posted : Wednesday, 24 November 2010, 09:59 - Mark Unread
Jayenkai
Does..
color int(pop()),int(pop()),int(pop())
.. make a difference?

-=-=-
''Load, Next List!''
Posted : Wednesday, 24 November 2010, 10:28 - Mark Unread
Tikihead
...will skip some of them and then jump back to evaluate them later.

That's exactly what's been happening, thanks for the solution DD. I guess I've either never noticed this problem until now or I've just been lucky.

@Jay - Nope, that doesn't help.
Posted : Wednesday, 24 November 2010, 18:02 - Mark Unread
Tikihead
Now I think something is actually wrong - a file compiled and run immediately runs the code below fine, but a file compiled to an exe and run by itself gives an error.


Posted : Wednesday, 24 November 2010, 18:03 - Mark Unread
Jayenkai
Hmm.. sounds a wee bit screwy. What's your version?

-=-=-
''Load, Next List!''
Posted : Wednesday, 24 November 2010, 18:06 - Mark Unread
Tikihead
1.100 - this just started happening yesterday, which I think is rather odd.

|edit| I figured out that there must be something wrong with my operating system that somehow translates to not being able to allocate memory for my program to run.

My program takes info from the command line (it needs a file to open to start) and depending on how I give the file to it (drag file onto the exe or right-click on file and choose "open with"), it will draw the image or it'll spit out an error. |edit|