OSDev.org

SoLDMG wrote: Operating system development is like reinventing the wheel and making it square. Like I'm doing, and you probably too.
How's your square wheel coming along?

Square Wheel:

alexfru wrote:

SoLDMG wrote: Operating system development is like reinventing the wheel and making it square. Like I'm doing, and you probably too.
How's your square wheel coming along?

Square Wheel:

...

Well I'll be a bat out of hell.

wheels are too mainstream

DaemonR wrote:wheels are too mainstream

*flips hipster scarf around neck*
Sir, that is awesome. If that was an operating system it'd be Windows 9000, NT version 15.728. And it'd include the guy on the hover-thingy flying over a banana peel and then for some reason falling over, because Windows logic

Back to the point, I like to think my syntax looks really clean. Might just be owners pride though.

SoLDMG wrote:

b.zaar wrote:If you are not using the characters ; or # or // for another purpose why are you creating a new comment character?

It looks nice, I guess. And what would you want it to be? Just getting as much feedback as possible.

Changing a syntax with the rest of the instructions may suit your personal taste, but changing something this simple that everyone already knows for little or no gain seems senseless. Also on my keyboard reaching for ! (with shift) isn't as easy to reach as ; or // (without shift) when typing.

I guess I just prefer to keep things simple when they already work.

b.zaar wrote:Changing a syntax with the rest of the instructions may suit your personal taste, but changing something this simple that everyone already knows for little or no gain seems senseless. Also on my keyboard reaching for ! (with shift) isn't as easy to reach as ; or // (without shift) when typing.

I guess I just prefer to keep things simple when they already work.

I second this. The best reference when planning to change or alter how a person is going to do something, or introduce a new concept is to stick to the structure principle of user-interface design

Don't ever change something that works just to be different. Only change it if you have a new innovative idea to replace it, and if the way you are incorporating it won't disturb the user's workflow.

b.zaar wrote:If you are not using the characters ; or # or // for another purpose why are you creating a new comment character?

! for line comments isn't anything new except maybe on Intel platforms. If you have SPARC background, you'd just love it.

fronty wrote:

b.zaar wrote:If you are not using the characters ; or # or // for another purpose why are you creating a new comment character?

! for line comments isn't anything new except maybe on Intel platforms. If you have SPARC background, you'd just love it.

It's also used with the as86/as386 assemblers, I've heard.

DaemonR wrote:

b.zaar wrote:Changing a syntax with the rest of the instructions may suit your personal taste, but changing something this simple that everyone already knows for little or no gain seems senseless. Also on my keyboard reaching for ! (with shift) isn't as easy to reach as ; or // (without shift) when typing.

I guess I just prefer to keep things simple when they already work.

I second this. The best reference when planning to change or alter how a person is going to do something, or introduce a new concept is to stick to the structure principle of user-interface design

Don't ever change something that works just to be different. Only change it if you have a new innovative idea to replace it, and if the way you are incorporating it won't disturb the user's workflow.

Jeff Raskin is a boss. Too bad his Canon Cat computer didn't break through like the
Macintosh did.

I've chosen to introduce the ".comment" directive. The character that is specified after it will be considered the new comment character, so in theory many people with many assembly backgrounds will be able to write or read with at least the same commenting style. Or so I hope.

I suppose this is where I mention my own current assembler project...not that I've made much progress recently...