What programing language are you using? and why?

[Combuster]

And if you really know how it worked you'd know that using ELF or not is completely irrelevant to the features requested. Tell me, how is ELF architecturally incompatible with for example, the Java VM? In the end it's still binary code with attached symbols.

[hafai]

I use FASM with heavy use of the macro system. I've been implementing HLL style control structures and adjusting the syntax to something a little more readable with the macros. Not done with them though. I don't think I'll ever be done with them.

[melgmry0101b]

(for example singed, 100% virus-free executables, no stack overflow attacks (independent call and local variable stack), common license management etc.)

Really Perfect

[chibicitiberiu]

C and assembly. I prefer C++ or an object oriented programming language over C, but for the kernel I'm keeping it simple with C.

I use Cygwin with gcc and nasm. I love using an IDE with auto-complete, because I often forget how I name the functions, and I would constantly need to open/close headers, windows, and that's time wasting. That's why I name functions with long names (like ConsoleWrite instead of printf), to keep forgetting to the minimum. So I use Eclipse, with some batch scripts to build my kernel using a shell script, and run with virtualbox.

And I often change working OS between windows/linux, so these tools ensure I can work on both environments with a need of porting kept to the minimum.

[melgmry0101b]

C, ASM and Fortran, because they are easy to use and learn.

Is the fortran reliable for OSDEV?

[SDS]

That depends entirely on how competent a programmer is using the language - as always.

If someone was writing an operating system in FORTRAN 77 then I would be concerned for their sanity, and for the likely unstructured spaghetti-like mess that would likely result.

However, if they were making use of Fortran 95/2003/2008 to produce nicely modularised, structured and legible code then I can't see why not. The biggest issue with a lot of fortran code that is floating around is that such a large proportion of it was written by those who learnt to write code in an entirely utilitarian manner with FORTRAN 77 many moons ago, and haven't updated their practices since...

That said, it doesn't exactly lend itself to systems programming - it is much more suited to dealing with large amounts of data in a computational sense. Hence its use for such a large proportion of computational scientific work. (Said while editing a code with 50028 lines of Fortran 90, 12180 FORTRAN 77, 1430 C++).

*edit* - fix typo

[ACcurrent]

This is my first post~ anyway. I use c for the core kernel and I am developing my own JIT language for the drivers.

Code: Select all

import System.Driver
request: runlevel=1
namespace driver_x{
Struct DriverHeader{
        DriverName = Something
}
write(){
     driver.outb(Var x,Byte *x);
}
}

BTW: CL looks cool

[melgmry0101b]

This is my first post~

Welcome

[miker00lz]

since my OS is targeted at real-mode machines, i'm using the ancient Borland Turbo C++ 3.0 compiler and TASM.

but even though the old Borland IDE was badass in 1990, i'm doing the actual writing of the code in Dev-C++ IDE and wrote a .bat file to actually run my toolchain... which includes a little QB app to convert the output .EXE to a raw binary then build a floppy image from that and my boot sector.