Re: RosAsm Team is Still Making Excuses


<randyhyde@xxxxxxxxxxxxx> wrote:

[totally misunderstood...]

| .... 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.

If you like to have a consecutive set of bytes, then just
declare them within a line.
[MyBytes: B$ 0 1 2 3 4 5]
BU_ASM_Help says: 'a new line forces DW-alignment'.

Hard to understand for the 'not that smart' ?

| 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.

There are that many source-code examples of any style,
that everyone who's really interested in, can find out
how it works without too many questions.
Of course a minimum of logical thinking is required.

| 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).

If you would be seriously interested in RosAsm, then you wont come
up with that sort of questions.
Ask the (your?) Governor how to succeed with a low IQ :)

| 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.

The 'casual' reader is warned on top: "work in progress".

| So, if you've got some amazingly good information about RosAsm's
| behaviour that contradicts what the documentation says, feel free to
| share it with us.

Yes, the documentation is somehow behind the actual status
(as usual for projects in progress).

I didn't find any wrong statements in BU_ASM, Ok, some parts are
missing and a few had to be read twice due a bit French influence.

__
wolfgang


.

Relevant Pages

  • Re: Structures in Assembly Language
    ... > This declaration looks very strange to me... ... Looks like a very queer way of ... It doesnt reflect on RosAsm, ... I dont have to reoffset every single member while the code ...
    (alt.lang.asm)
  • Re: Release of RosAsm V.2.029d
    ... Indeed RosAsm does not need any Linker, ... directly output a PE in the Click-Time. ... It also does not need any declaration of Win32 ...
    (alt.lang.asm)
  • Rene has written a custom edit tool for RosAsm
    ... ' RosAsm, The Bottom-Up Assembler for ReactOS -V.1.22b-' 0] ... declaration in RosAsm. ... The fact that something is named EditClassName does not mean that it is used as a base class for any window. ...
    (alt.lang.asm)
  • 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)