From: Frank Kotler <fbkotler@comcast.net>
To: linux-assembly@vger.kernel.org
Subject: Re: hla
Date: Fri, 10 Mar 2006 18:16:06 -0500 [thread overview]
Message-ID: <441208B6.9070808@comcast.net> (raw)
In-Reply-To: <20060310203259.GA7399@wintermute>
leslie.polzer@gmx.net wrote:
> On Fri, Mar 10, 2006 at 12:18:55PM -0800, Tim Hoolihan wrote:
>
>>I posted some info on my sight about hla, and was curious if anyone
>>on here has tried it? I've used mainly gas and nasm, but this seems a
>>convenient way to use them.
>
> HLA is an educational tool used in the book "The Art Of Assembly".
> I don't think anyone uses it in serious production.
What assemblers do folks use for "serious production"?
While HLA *is* designed as an educational tool, it's pretty "powerful",
and would be suitable for "serious production" if you wanted to.
> Besides, IMHO it's quite ugly :D
Well... beauty is in the eye of the beholder! I wholeheartedly agree,
though! :)
Regarding Tim's correction to the install doc: Good point! That's new -
the last version wanted you to be in /usr. This one wants /. Best to
check. I don't think Randy's got the "packaging" for Linux down pat. I
add version numbers when I download 'em, for example...
I haven't used HLA much. I don't crave the kind of "power" it offers,
and... okay, it's ugly. Since it will produce code that will run on
*either* Windows or Linux, I think it's an "interesting" tool/toy. It's
the HLA Standard Library that allows it, of course. Ported to Windows
and Linux, with more OSen planned. We can call the C library, of course,
but some people might prefer a library written in asm (HLA, to be sure,
but recognizably asm). Call it, or read it to find out how things might
be done - I do more of the latter. :)
Best,
Frank
next prev parent reply other threads:[~2006-03-10 23:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 20:18 hla Tim Hoolihan
2006-03-10 20:32 ` hla leslie.polzer
2006-03-10 23:16 ` Frank Kotler [this message]
2006-03-13 16:29 ` hla Tim Hoolihan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=441208B6.9070808@comcast.net \
--to=fbkotler@comcast.net \
--cc=linux-assembly@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox