Author Topic: OT Basic  (Read 73107 times)

0 Members and 1 Guest are viewing this topic.

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: OT Basic
« Reply #75 on: March 21, 2011, 02:34:04 pm »
I like some aspects of it being OOP, but more like a struct than an actual object with methods and such, like it is in Java.

Offline fb39ca4

  • LV10 31337 u53r (Next: 2000)
  • **********
  • Posts: 1749
  • Rating: +60/-3
    • View Profile
Re: OT Basic
« Reply #76 on: March 21, 2011, 02:39:08 pm »
true.  Maybe a lowercase b/h?  or %/$?

I think %/$ would be a good idea. They're hardly used in other situations.

Unless we want to make them actual operators? :D

EDIT: Btw, who's actually working on this?
% might be used as the modulus operator, like in C. @ could be used as well

Offline jnesselr

  • King Graphmastur
  • LV11 Super Veteran (Next: 3000)
  • ***********
  • Posts: 2270
  • Rating: +81/-20
  • TAO == epic
    • View Profile
Re: OT Basic
« Reply #77 on: March 21, 2011, 10:21:06 pm »
true.  Maybe a lowercase b/h?  or %/$?

I think %/$ would be a good idea. They're hardly used in other situations.

Unless we want to make them actual operators? :D

EDIT: Btw, who's actually working on this?
% might be used as the modulus operator, like in C. @ could be used as well
Yeah, that's true.  Hmm.  @ for modulus or binary?  I could live with mod like you have and/or/xor in Z80 basic.

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: OT Basic
« Reply #78 on: March 26, 2011, 11:15:39 pm »
Personally I think there needs to be alternatives to floating points too, maybe even through MODE changes (float, fix 0-9, integer 1 byte through 4 unsigned, etc). Because one major issue with BASIC is that floating points are huge. In a list, a floating point number is 9 bytes instead of 1 for a 1 byte integer. I think there should be support for 1, 2 and maybe even 4 bytes integers, and why not nibbles/binary while we're at it?