New to os dev

[python]

Im new soooo..ill start asking questions.

1 where is the best place to learn asm

2. what is the best asm compiler fasm(i like this one),tasm,nasm?

3.What is needed to write an os.

I know python(ok im not an expert but ohhwell

[JAAman]

2. i personally like nasm but it depends on you: basically the best tool to use is the one you are most familier with and comfortable working with

3. a brain! no really you should get the intel manuals and RBIL:
1

## ---- ----- ------ Intel Manuals

## ---- ----- RBIL


learning ASM is very important though most people don't use it much its important because it forces you to learn how the CPU operates

as for codding most people use C (although many try C++ and it is posible but many also give up on C++)

me i try to get as close to the CPU as possible (as little abstraction as possible) so i use ASM and (eventually) some C (prob MS C compiler stripped to bin format)

[Legend]

Well, C++ without exceptions and RTTI is not really a problem!

[JAAman]

i did say its possible but even solar (@mega-tokyo) said unless you REALLY want C++ its better and easier to use C

basically it comes down to what languages are you most compfortable with (and for me there is no way i'll ever be compfortable with ANY oop language:)

truth is it wont make any difference to your application developer, or even later-on your osdev, which language you use

btw: i like nasm because it doesn't try to second guess what your trying to do -- its output is always exactly what you tell it to do (and it uses the simpler and more consistant intel syntax, which reminds me of the 6502 where i first learned ASM)

[Legend]

Well, I would not consider any language that can't really help with oop
I'm really too lazy to do it by hand like 99% of C apps do.

[python]

Ive chosen fasm after looking at all of them. Is there any good tutorial for asm? Also where is the best tutorial for writing a bootsector?

[carbonBased]

You say you know python, but do you actually know C?

I don't want to be a downer, but I always like to suggest that an OS is *not* a good choice as a first project for learning any language. Also, even if asm isn't your primary language, learning asm while written an OS makes most tasks that much more difficult.

Cheers,
--Jeff

[python]

well im about half way through learning python. I am going to learn asm before I do any os coding.

[JAAman]

learning ASM is a very good idea, but knowledge of a higher level language is a must and python isn't likely to help you much (except, posibly, helping to learn basics of programming - not sure since i don't know the language)

C is good becase most people use it, so its much easier to get help with it (in fact i'd say knowing C is a must even if you don't use it, becase it enables you to read and understand everyone elses code)

[python]

is yasm any different than nasm?

[JAAman]

iirc its similar (and uses Intel systax)
not sure about it (never used it)

is there a reason you don't want to use NASM? (its just you keep mentioning that you want to use different assemblers, but seem to be avoiding the most popular one)

[python]

NASM is written in c what kind of self-respecting asm programmer would use an assembler written in C?

PS Ive heard this said in many places...

[carbonBased]

There's nothing wrong with an assembler written in C.

In my opinion, it's the smartest approach. You have access to libc, and development times are stripped. Not to mention, it makes it easier to add third party object formats (of which nasm supports many).

A 'self-respecting asm programmer' will chose an assembler based on other criteria, I'd imagine.

--Jeff

[JAAman]

a 'self respecting asm programmer' will use whatever tools are best for the job

regardless of the language its written in -- who cares!

if your really concerned about the language your tools are written in then OSdev is definately not for you -- there are much more important things to be concerned with

if it works, use it!

[python]

Just saying what I heard...

PS FROM MANY PLACES...9 places