RosAsm Team is Still Making Excuses


\o//annabee wrote:

> > These two declarations actually wind up consuming eight bytes in
the
> > address space rather than two. Hardly intuitive. Hardly what anyone
> > would call "true" assembly. This seems to suggest that the default
> > value that RosAsm uses for alignment is incorrect.
> >
> > Perhaps this is yet another reason assembly programmers aren't too
hot
> > on switching over to RosAsm. Heck, even HLLs don't do this. So if
> > you're expecting HLL programmers to switch to RosAsm, the first
thing
> > they're going to ask is "why do byte variables consume four bytes
in
> > the address space?"
>
> I think you TOTTTALLLLLYY misunderstood everything here :))))

It's quite possible. The RosAsm documentation isn't exactly the best
example of great documentation I've ever seen. But it *certainly* seems
to imply that variables in separate declaration sections are aligned on
dword boundaries. Furthermore, Rene's post seems to verify this. If
you have other information about the operation of RosAsm in this
regard, feel free to post it.

It's pretty clear that the RosAsm crowd thinks they are an elite bunch.
Every time a perceived problem is posted to this newsgroup the response
seems to be

1. Well, you just don't understand how to use RosAsm.
2. Your IQ isn't high enough to understand what's going on.
3. That could be fixed by one instruction, but we're not going to do it
because we know how to work around the problem and you don't.
4. etc., etc., etc.

The interesting part is what this posts *don't* include. Namely, things
like:

1. Here's how you do this in RosAsm
2. Here's an explanation that someone who only has an IQ of 80 can
understand.
3. Here's the corrected version of the software (or the work around
that we all use).

This leads the casual reader to assume:

1. The RosAsm team doesn't understand the problem either.
2. The RosAsm team can't figure out this stuff, either.
3. The RosAsm team hasn't got a clue how to fix the problem.

So, if you've got some amazingly good information about RosAsm's
behavior that contradicts what the documentation says, feel free to
share it with us. RosAsm can be forgiven for having "out of date"
documentation. But statements like "I think you TOTTTALLLLLYY
misunderstood everything here :))))" is absolutely meaningless without
proof that *you* actually understand what is being discussed here.

Granted, I'm having trouble getting my point across. People much
smarter than you haven't grasped exactly what it is that I'm trying to
push here. But at least their posts suggest that they're following the
general discussion. As usual, *your* posts are just a bunch of empty
words that were probably written without even reading the actual
original post. That's okay. It's a good excuse to (one more time) point
out some failings in RosAsm and the RosAsm development methodologies.
Cheers,
Randy Hyde

.

Relevant Pages

  • Re: Linux, X, ld, gcc, linking, shared libraries and stuff
    ... > This is a real problem with SoftWare (not only RosAsm), ... > some quantity of Functionalities, ... the harder it is to "keep up" with the documentation... ... >> powerful macro system (you know, perhaps you don't feel it's better ...
    (alt.lang.asm)
  • Re: RosAsm Team is Still Making Excuses
    ... RosAsm is no different on this matter. ... What I'm saying is that if the documentation says one thing about the byte alignment issue *AND THIS IS INCORRECT*, feel free to correct me on that. ... RosAsm *still* aligns bytes in a declaration section of their own on a dword boundary when there is no need for this. ... because the program uses more cache space). ...
    (alt.lang.asm)
  • Re: RosAsm Team is Still Making Excuses
    ... > declare them within a line. ... you just don't understand how to use RosAsm. ... the documentation is somehow behind the actual status ... because the program uses more cache space). ...
    (alt.lang.asm)
  • Re: Is MASM32 an evil Microsoft plot?
    ... Herbert Kleebauer écrivait ... > and in a last step wrote the Windows assembler version. ... this "Documentation"? ... Now, if _you_ cannot wait, you can run RosAsm, load ...
    (alt.lang.asm)
  • The Case Against RosAsm (#9)
    ... RosAsm Doesn't Do Structures ... Some bad Assemblers have a "STRUCT" KeyWord performing hidden Declarations ... What is effectively done by the Assembler would be expressed, ... the right Edit Control gives you the Structure Equates translation. ...
    (alt.lang.asm)