Hi,
thanks for your time to answer.
There is some peculiarity in the way assembly language goes the path that makes a great value in its own to learn about it (also only making in the least, experiments)
That said I think that good references always matter and, given the ten galaxies of details that come in the trade, some effort to expose to the relevant parts at relevant stages, can make the difference and smooth the barriers to successive milestones.
This could not be true for all of us, but I do not find the 64-ia-32-architectures-software-developer-manual-325462 with its 3355 pages, together with some unguided effort, the best way to get knowledge in the pocket.
I am new in the assembly field, but the shortage in good bibliography especially in advanced topics , apart of long references, is a major issue. Behind a good book there is great effort to supply a framework and an anticipated list of topics to form a consistent subset of knowledge , relying on previous (if any) blocks of the whole body.
What is advanced and what is not is obviously questionable, but there are always things that can be safely ignored while starting something, and become relevant later. Up to now I only know a subset of the instruction set and concepts and am able to write some useful thing, later this will no long suffice as the perception of being able to get something bigger in the pocket will arise.
Curiosity without a plan won't work.
Saying that bibliography does not matter is the same to say the colleges do not matter. One starts to really learn when starts to play with his/her own instructions and problems, but this is quite facilitated by efforts in providing good material and orientation, as both colleges and books do (aware that both will only help, some time in substance).
Starting alone again, with a cpu and a brick of a-z ordered reference material can be fun, but sure not efficient .
Hi!
Well, I think assembly is assembly, there is no such thing as intermediate/advanced or professional.
Also there are not only one way or only professionals way, how to solve certain problem.
There are N problems and N solutions for each of them.
It's all about you, your creativity and YOUR experience and how much time you are willing to spend learning new things.
Storage handling and I/O - they are general terms, you can handle storage and i/o in your own way.
One knowledge leads to another, one experience leads to another.
I currently sometimes read and consult pdf books like "Intel® 64 and IA-32 Architectures",
for example, one from the books is: "Intel® 64 and IA-32 Architectures Software Developer’s Manual".
There is also good reference for instructions, Streaming SIMD Extensions and so on.
Bye, Encryptor256!