Re: HLA StdLib2 criticism


Betov wrote:
"santosh" <santosh.k83@xxxxxxxxx> écrivait news:1169052135.949847.265240@
38g2000cwa.googlegroups.com:

An advantage of object code over source snippets is that, assuming it's
written to a standard ABI, it can be used from all assemblers, and even
HLLs, whereas, the snippets collection will, by it's very nature, be
specific to a particular syntax and/or assembler.

At the cost of loosing the Asm control...?

Wait, I thought your "disassembler" (and I use that term *very*
loosely) would solve this problem? Have you finally faced the fact that
a disassembler approach won't work and you've given up on that pipe
dream?


Porting in between the actual Assemblers is not a real
difficulty.

Then why has it not been done? Except for HLA, which can emit MASM,
FASM, TASM, and GAS code, and a few aborted attempts that don't work
well (like intel2gas or gas2Intel), I've seen no such products that do
what you claim to be so simple. And it isn't because people don't want
this capability.

In a kind of "generic Assembly", without Macros,
there are not significative differences in between NASM,
FASM, RosAsm (which accepts a alternates generic syntaxes),
and GoAsm.

Really? And how much code have you tried to port between these
different assemblers? Links, please. About the only thing they have in
common are mnemonic names and operand ordering. If it were as easy as
you claim, why are the so many questions from FASM beginners who are
using some NASM code they've found?



Maybe (probably, talking of VID "doing a good work"...), but
this is an HLL Method, that does not interrest me, at all.

It was an "assembly method" long before it was a "HLL method." You do
realize that, don't you? Again, the only reason you have for claiming
it's a "HLL method" is because your own product doesn't support the
ability to link in static libraries.

By
the way, if this new .lib is better than the HLL ones, why not
proposing it to HLLers, instead of Asmers?

Because it's being written for assembly language programmers and won't
even link with HLLs?


You can keep 100% sure that the MASM user will never use it,

Why do you say that? There are some MASM users out there using the HLA
standard library. Why wouldn't there be some who use FASMLIB? That's
the beautiful thing about object code -- it's assembler syntax
agnostic.

and
that the FASM user will never use the Paul Brennick one.

Why not? All it takes is a header file for FASM with the appropriate
declarations.


Each
one will have its own one.

And smart programmers will realize that they can pick and choose from
the best of all of them. Indeed, there is no reason on earth why a
single application couldn't call some MASM32lib code, some FASMLIB
code, some Genesys code, and some HLA stdlib code. That's up to the
application designer, not the library designer, and certainly not the
assembler designer.


So, why talking of something general
scope (a "universal Asm.lib"), in an area where "universal" never
existed and never will exist?

Universal does exist. It's called object code. It's called a
"statically linked library." Again, you simply refuse to acknowledge
such a thing because your own tool won't support it.


It would even be a surprise to me,
if the VID's library could become "universaly admitted" in the
FASM camp...

Yes, assembly language programmers are notorious for wanting to
"reinvent everything from scratch" on every project. That's why we
don't see too many large assembly projects ever complete. It's why a
product like FRESH didn't quite make it but a product like HIDE *has*
made it. Having appropriate library code can make all the difference
in the world in a large project. It would seem to me that you would be
all for creating libraries to support large application development, as
you're the one constantly pushing people to develop "full" applications
in assembly language.
Cheers,
Randy Hyde

.

Relevant Pages

  • Re: Write Great Code Appendixes are on-line
    ... The simple fact is that all Assemblers (but one that nobody ... what could be the purpose of an external HLL ... was really to improve the Macros System capacities, ... that may be run on the programmer ...
    (alt.lang.asm)
  • Re: Faster HexToBuffer Routines
    ... Since the example said "real assembly programmers" I asked if you ... If you fail to understand that Optimizing at a Code Level is ... specific to HLL Code, because any HLL is based on the Concept ... the fastest of the actual Assemblers. ...
    (alt.lang.asm)
  • Re: RosAsm Just Cant Compete with any assembler (this is news?)
    ... >>> FASM users do you think would be willing to switch over to RosAsm? ... There are two main families of Assemblers: ... HLL Medias. ...
    (alt.lang.asm)
  • Re: I think i finally got a definition of an Assembler!
    ... An assembly language that also uses keywords, ... > True High Level assemblers are included in Macro Assemblers. ... > is a HLL, so its not merly a macro assembler/High Level Assembler. ...
    (alt.lang.asm)
  • Re: Percentage of programmers using which asm compiler? (Windows)
    ... > There's quite a handful of different assemblers for Windows out there (for ... MASM - probably hundreds of thousands of casual users. ... NASM - Probably 10-30,000 casual users. ... FASM, HLA, GoAsm probably have ...
    (alt.lang.asm)