Insert a chapter in NASM documentation to explain one
idea on how to perform OOP in NASM under Linux (at
first, add other systems later) just using a couple
macros and structures.
Thanx,
I've looked at it briefly, but not enough to "get" it.
Why Linux, at first? Judging from the download counters,
most of our users are on Windows. Is there much/any
difference between OOP under Linux and OOP under Win32 (or
MyHomeMadeOS, for that matter)?
The Nasm Manual isn't really intended to be a "How to
Program" manual, but maybe this innformation would fit under
"macros" or "structures" (or both?). Ideally, it might fit
better in the "Archive of Auxilliary Documentation,
Tutorials, And Examples for Nasm". But since that doesn't
exist...
You sound as if you've got some idea what should go in this
hypothetical chapter. Can you write something up? If it's to
go in "the" manual, I can help bash it into Nasm's ".src"
format, if need be.
I think some info on "How to do OOP in Nasm" would be a
great idea, but it might be better as a separate document.
My concern is that the manual is getting rather large, and
I'm afraid if it gets much bigger, no one will read it at
all (if they do now)...
In any case, thanks for the idea, Bruce.
Best,
Frank
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=68913
I'm afraid the only thing I know about "OOP" is it's what I
say when I make a mistake :)
Jones Henry has got some info on using Nasm for OOP
http://www.geocities.com/sjhenry/
I've looked at it briefly, but not enough to "get" it.
Why Linux, at first? Judging from the download counters,
most of our users are on Windows. Is there much/any
difference between OOP under Linux and OOP under Win32 (or
MyHomeMadeOS, for that matter)?
The Nasm Manual isn't really intended to be a "How to
Program" manual, but maybe this innformation would fit under
"macros" or "structures" (or both?). Ideally, it might fit
better in the "Archive of Auxilliary Documentation,
Tutorials, And Examples for Nasm". But since that doesn't
exist...
You sound as if you've got some idea what should go in this
hypothetical chapter. Can you write something up? If it's to
go in "the" manual, I can help bash it into Nasm's ".src"
format, if need be.
I think some info on "How to do OOP in Nasm" would be a
great idea, but it might be better as a separate document.
My concern is that the manual is getting rather large, and
I'm afraid if it gets much bigger, no one will read it at
all (if they do now)...
In any case, thanks for the idea, Bruce.
Best,
Frank