Pete's QBASIC Site

?

2008-04-20T17:17:17-05:00

Once again for the umpteenth time, I have the feeling I'm missing something .

Statistics: Posted by Mentat — Sun Apr 20, 2008 5:17 pm

Re: wow.. odd

2008-04-17T07:26:32-05:00

That is weird..

Kinda like a mix of a FNExpression and.. something..

Constructicons.. unite!

hahaha..

^~^

Thanks very much for the detailed info on how to use it. I may consider using it now that I know what it is.

It's pretty much a method that runs at the start of being DIMed.
And a deconstructor is the opposite.

Statistics: Posted by Mentat — Thu Apr 17, 2008 7:26 am

Who are you talking to KYOTE?

2008-04-16T22:30:06-05:00

I think nobody is listening anyhow LOL

Statistics: Posted by burger2227 — Wed Apr 16, 2008 10:30 pm

wow.. odd

2008-04-16T22:23:16-05:00

That is weird..

Kinda like a mix of a FNExpression and.. something..

Constructicons.. unite!

hahaha..

^~^

Thanks very much for the detailed info on how to use it. I may consider using it now that I know what it is.

Statistics: Posted by Kiyotewolf — Wed Apr 16, 2008 10:23 pm

Odd Buffer problem

2008-04-16T17:02:34-05:00

you lost me at constructor..

isn't that a transformer toy?

constructor.. FB keyword??

A constructor is a special kind of procedure. And it's a keyword.
Such as

Code:

TYPE dog     'some data     age AS INTEGER     weight AS INTEGER          'sets up weight, and sets age to 5     DECLARE CONSTRUCTOR(AS INTEGER)END TYPEDIM AS dog fluffy=dog(12)DIM AS dog kit=dog(15)PRINT "Fluffy's age is ";fluffy.agePRINT "Fluffy's weight is ";fluffy.weightPRINTPRINT "Kit's age is ";kit.agePRINT "Kit's weight is ";kit.weightSLEEPENDCONSTRUCTOR dog (someWeight AS INTEGER)     weight = someWeight     age=5END CONSTRUCTOR

And the output would be

Code:

Fluffy's age is  5Fluffy's weight is  12Kit's age is  5Kit's weight is  15

Thanks coderJeff.

Statistics: Posted by Mentat — Wed Apr 16, 2008 5:02 pm

Odd Buffer problem

2008-04-16T08:53:01-05:00

fbc doesn't do overflow checks (even with error checking enabled). The size of the result is same as whatever the largest numeric type is in the (sub)expression.

Code:

dim as short x, yx = 640y = 480print x * y * sizeof( integer )print cint(x) * y * sizeof( integer )'' OUTPUT:'' -81920''  1228800

Statistics: Posted by coderJeff — Wed Apr 16, 2008 8:53 am

huh?

2008-04-16T01:16:46-05:00

you lost me at constructor..

isn't that a transformer toy?

constructor.. FB keyword??

Statistics: Posted by Kiyotewolf — Wed Apr 16, 2008 1:16 am

Odd Buffer problem

2008-04-15T14:55:55-05:00

I've been having a weird Allocation problem.

If I store 640 in a short var wdth, and 480 to a short var height (screen dimensions), and then ask to allocate, the bugger fails.
If I ask to allocate a 640*480 buffer, it continues.

However, the first case works if the dimensions are smaller (but I'm not going to work with a 100*100 screen, people).

Here's some abridged code

Code:

DIM AS main something = main (640,480)'blah blah blahCONSTRUCTOR main (wdth_ AS SHORT, height_ AS SHORT)     wdth = wdth_     'both are SHORT     height = height_     SCREENRES wdth, height          'buffer     buffer = ALLOCATE (wdth * height * SIZEOF (INTEGER))END CONSTRUCTOR

This one didn't work. The buffer was null and empty.

This one did work:

Code:

DIM AS main something = main'blah blah blahCONSTRUCTOR main     SCREENRES 640, 480          'buffer     buffer = ALLOCATE (640 * 480 * SIZEOF (INTEGER))END CONSTRUCTOR

The resulting buffer was in good working order. The latter is nice if I am going to use 640*480, but that won't always be the case. The former is good for stamps.

Statistics: Posted by Mentat — Tue Apr 15, 2008 2:55 pm