tremblin's Blog

Blog

  • u tubs are banned

    u fat tubs have been banned for years. Get off the site tubby!

  • I Finally Upgraded My Internet

    I had 15 down/3 up for about 20 years. Then I slightly upgraded to 25/25 for 6 years… still nothing like my now 250/250 which feels like I’m in the current century now… Nothing like uploading 7-8 different ports of a game every week on 3 up… I have waited around for an eternity.

  • BooBoo 2.4.5

    C style multiline comments (/* */) were added. Also improved flexibility of all comments with a few corner cases where they weren’t supported being fixed.

    Added a not operator (!).

    The address function was removed in favour of the address operator (@).

  • Valve Boss Needs Shave, Haircut and Bath

    gabe Newell needs a haircut a shave and a bath …

  • Should I revert “real” references?

    I can’t see any point when you can use pointers. Is there any use case for them? In case you aren’t aware, the last change I made to BooBoo had references that you could take the address of and get the address of the variable passed as a reference… C++ doesn’t have these kind of references and there is a significant overhead when doing it. So I want to remove them unless there is a reason I don’t think of. Anyone?

    Update: Now it’s done (2.4.4.) The address operator (@) remains but references aren’t such a CPU pig again. Reference values are copied back into the appropriate place after the function ends instead of rewriting variables to refer directly to the original value, since there doesn’t seem to be any value in it when pointers are available.

    The @ operator is shorthand, which can be used to easily pass pointer values into a function. Instead of:

    pointer p
address p var
call foobar p

    You can do:

    call foobar (@ var)

    You could replace use of address with @ if you want:

    = my_pointer (@ var)