OSDev.org

Aidhus wrote:THAT is the OS platform.

I think MessiahAndrw wants to know what hardware platform you are targetting.

Combuster wrote:

My Operating System

<sarcasm> Really? </sarcasm>

Yes,
Please don't use <sarcasm> it's like an HTML tag, in books and writing sarcasm is denoted by:

Really?

And yeah it's not yet another "MIKEOS Clone" (YAMC), it's what I call POS-64 (The Portable Operating System for x64)
BTW Just got a useless/useful/very tough to implement VFS working on a useless FAT12 Floppy (I know FAT12 is useless and would soon upgrade to FAT16 (Simpler don't have a nibble to deal with) :

To be honest, I didn't write everything (but I wrote at least something) stuff borrowed from BareMetal,MikeOS,Linux
I accept I am a n00b, but that's how everybody starts with (right?), even Linus Torvalds was a noob at programming at sometime isn't it?

sid123 wrote:I accept I am a n00b, but that's how everybody starts with (right?), even Linus Torvalds was a noob at programming at sometime isn't it?

At the beginning, Linus Torvalds wrote everything by himself and so did most of us. Of course, it is perfectly all right to borrow code from other projects if licenses allow it. However, it is not required to get started. It is much more fun to say "I wrote it".

Antti wrote:It is much more fun to say "I wrote it".

+1

Antti wrote: It is much more fun to say "I wrote it".

And when you write it yourself you have a much better chance of actually understanding it. I really need to implement in order to understand. There's more than a few ideas that I thought I understood until I actually implemented them for myself which exposed my misconceptions. I suppose it's just me paying my dues.

I added syntax highlighting to my editor:



It's a pretty hacky and complicated state machine, but it does the job for C and C++. The color scheme isn't entirely optimal, I had to do with some VGA colors here. The red line to the right is the right margin, in this case set to 80 columns. But overall, this is much better than just white text and it even makes my editor seem somewhat usable. And yes, that's a "do if" statement because I like to write what other people see as crazy code.

sortie wrote:And yes, that's a "do if" statement because I like to write what other people see as crazy code.

Wow. It took me a while to see that it is even valid C syntax.

Hi,

Aidhus wrote:ZTE OPEN

That sounds interesting; can you share more about your OS (is it hosted somewhere)? Also, how easy was it to find information (datasheets, and so on) for the ZTE Open?

Regards,
Shikhin

do if sucks.

do!
do class!
do class if!

that's the right way

Hobbes wrote:

sortie wrote:And yes, that's a "do if" statement because I like to write what other people see as crazy code.

Wow. It took me a while to see that it is even valid C syntax.

It's C++!

@Sortix: You use C++? Realized that just today, after looking at your screenshot and then hurrying over to your git repo.
Actually, after reading Bjarne Stroustrup's Bible on C++, I realize that I should have written my OS in C++. (at least partly. It's not a big problem switching now, my OS is at ~9k lines right now. But requires some design re-thinking. Maybe I should keep some low-level C layer?)
(at all those C programmers: C++ is fun! It's like you had to talk in Chinese for years and then finally switch to English and can express your ideas freely.)

tiger717 wrote: It's C++!

Not really, look at all those #defines, it's just C with classes.

My OS in D lang now supports multitasking.



https://github.com/Bloodmanovski/TrinityOS

tiger717 wrote:@Sortix: You use C++? Realized that just today, after looking at your screenshot and then hurrying over to your git repo.

dozniak wrote:Not really, look at all those #defines, it's just C with classes.

Yes, I use C++. I don't use that many C++ features in the kernel and sometimes in "C with classes" ways, but that is mostly because of old mistakes of mine and because I don't trust all C++ features yet (and some are unavailable because I hadn't added support for some runtime things). Mind you that the #defines used in that particular screenshot is part of a very ugly hack to load kernel symbols - it's not good design - but rather intended to keep lines from getting longer than they already are. I need to revise large parts of my kernel, still. My user-space is written in C-style C++ - though - which is because I can write such code very correctly, but also that my libstdc++ port is not available in the mainline release yet.

New Version, POSx86 0.6.7.2 (It says 0.5.1.2 but it is 0.6.7.2):
(Not to Public Yet )

It has External Floppy Support with FAT16 Hard Drive Support, (Write-Back Support Not available yet, So the assembler writes the files to the external floppy for the _sake_ of assembling )