[Vultra]

Hello all,

Just got a quick question since, i'm in a rush.
Should I learn x84 & x64 first which isn't an issue or, do I have to learn C before going into that stuff?

thanks,

- Adam

[mothered]

C Is certainly advantageous to understand how to write simple programs, prior to moving onto Assembly.

@"phyrrus9" Is the best member to answer this In detail.

[phyrrus9]

C Is certainly advantageous to understand how to write simple programs, prior to moving onto Assembly.

@"phyrrus9" Is the best member to answer this In detail.

They're not mutually exclusive, you can learn both at the same time or later on. I would stay as far away from *86 assembly while you're first learning though. The entire architecture is garbage.

[Vultra]

C Is certainly advantageous to understand how to write simple programs, prior to moving onto Assembly.

@"phyrrus9" Is the best member to answer this In detail.

They're not mutually exclusive, you can learn both at the same time or later on. I would stay as far away from *86 assembly while you're first learning though. The entire architecture is garbage.

Thanks for the reply.

[mothered]

They're not mutually exclusive, you can learn both at the same time or later on.

I wasn't entirely sure whether one (particularly C) takes precedence, hence If anyone would know, It'd be you.

[Blink]

They're not mutually exclusive, you can learn both at the same time or later on.

I wasn't entirely sure whether one (particularly C) takes precedence, hence If anyone would know, It'd be you.

Late, but I'd personally do something like this:

Basic C or some other simple language -> Basic assembly in a simple architecture -> C -> assembly -> extra languages (Go, Lisp, Lua, Python, C#, whatever)

With basic CPU design somewhere in between the last 3; in this way, you get the full view of how your languages compile/interpret from high level down to hardware

There isn't really a precedence, you'd want to understand each on at least a minimal level

[Vultra]

They're not mutually exclusive, you can learn both at the same time or later on.

I wasn't entirely sure whether one (particularly C) takes precedence, hence If anyone would know, It'd be you.

Late, but I'd personally do something like this:

Basic C or some other simple language -> Basic assembly in a simple architecture -> C -> assembly -> extra languages (Go, Lisp, Lua, Python, C#, whatever)

With basic CPU design somewhere in between the last 3; in this way, you get the full view of how your languages compile/interpret from high level down to hardware

There isn't really a precedence, you'd want to understand each on at least a minimal level

Doesn't matter if you replied late. Thanks for the advice.

[mothered]

They're not mutually exclusive, you can learn both at the same time or later on.

I wasn't entirely sure whether one (particularly C) takes precedence, hence If anyone would know, It'd be you.

Late, but I'd personally do something like this:

Basic C or some other simple language -> Basic assembly in a simple architecture -> C -> assembly -> extra languages (Go, Lisp, Lua, Python, C#, whatever)

With basic CPU design somewhere in between the last 3; in this way, you get the full view of how your languages compile/interpret from high level down to hardware

There isn't really a precedence, you'd want to understand each on at least a minimal level

Well said.

I completely forgot to quote you. In my views, either yourself or phyrrus9 are best/competent In addressing questions of this nature.

[Slingshot]

Learning C will get you into the mindset of programming.

[Vultra]

Learning C will get you into the mindset of programming.  

I already know a few languages. learning SQL while we speak.