Re: RosAsm - right click

From: luvr (spam-loving-criminal_at_spam-sink.net)
Date: 05/06/04 

Date: Thu, 6 May 2004 18:53:43 +0100

"The Wannabee" <faq@.@.@.@.@.@szmyggenpv.com> wrote in message
news:opr7jy7rr2x4k3gu@news.broadpark.no...

> Yes you have the "impression". Its not based in logic or even thinking.
> _You_ are narrowminded, cause you make judgement based on what you prefer,
> rather then based on what works, and what is logic and intelligent. You
> choose Red over Blue. I choose logic over stupid. I am open, _you_ are
> narrowminded.

OK - If you want to think of me as narrow-minded, fine with me - I'm
sufficiently open-minded that I can live with that... :o) :o) :o)

> What you are really saying is you prefer to be stupid.

OK - If you want to think of me as stupid, fine with me - I'm sufficiently
smart that I can live with that... :o) :o) :o)

I just will *have* to, anyway, since by now, everybody will surely
understand that _you_ are the genius, and I'm the dumb sucker... Of course
they will - after all, it's a scientifically proven *FACT*... :o) :o) :o)

> What you say is completly wrong.

OK - You are right, as you always are, and I am wrong, as I always am.
Scientifically proven! :o) :o) :o)

> This is 2megas without any scoping or typing.

I could be wrong (well, I most certainly am - of course I am, since I always
am), but last time I looked, your so beloved science had evolved way beyond
two megabytes of monolithic source code without any scoping or typing...

> I agree. Its a convention. HLA is breaking a perfectly good convention.

Yes it does - And all those assemblers that want their operands in
'src,dest' order are breaking the equally perfectly good 'dest,src'
convention that got introduced long before by the IBM mainframe and its
assembly language. Now, kindly remind me - Which convention was the one
that was scientifically proven to be the only correct one again?

> But its the idiotic so damn insane parantesis that makes the top of the
> pie.

I could be wrong (well, again, I most certainly am - of course I am, since I
always am), but last time I looked, parentheses were a widely used and
agreed scientific (and, in particular, mathematical) notation for just about
anything. As a (self-proclaimed wannabee?) scientist, you should *LOVE*
them!

> So tell me, how does it store the words "Stupid idea, eh ?" in memory
> starting at 0_a0_0000 ?

Let me see... In ASCII, or in EBCDIC?
Or in Unicode, perhaps?
If in Unicode, little-endian, or big-endian?

Do you want the string null-terminated, or length-prefixed?
If length-prefixed, do you want one byte for the length? Two bytes? Or four,
perhaps?
If more than one, should the length be stored in little-endian, or in
big-endian order?
(Well - In case you prefer Unicode characters, I guess a one-byte length
prefix won't make any sense; but that still leaves two options. Furthermore,
the question about the byte ordering well be somewhat superfluous, since I
assume you will want to use the same ordering for the length as for the
string characters themselves.)

I could be wrong (well, again, I most certainly am - of course I am, since I
always am), but for a (self-proclaimed wannabee?) scientist, you are being
awfully imprecise here, aren't you? Or otherwise, kindly remind me - Which
string format was the one that was scientifically proven to be the only
correct one again?

> No what you accept is :
>
> mov ( inc ( mov ( ecx , ebx ) ) eax )
>
> and call it "easy on beginners". Thats what you do.

Did anyone ever tell you what a talented humourist you are?
Calling "mov ( inc ( mov ( ecx , ebx ) ) eax )" easy on beginners is just as
silly as calling "[iCall | mov eax #2 | mov eax D$eax | call D$eax+#1 #2
#3>L]" easy on beginners. (Mind you - I just randomly picked the first
RosAsm example I could find, so don't come yammering about the "far more
advanced RosAsm features" that the example demonstrates - I'm convinced
that, had I had the motivation, I could have come up with a far less
advanced example that was just as "easy on beginners.")

Of course, I could be wrong (well, again, I most certainly am - of course I
am, since I always am)...

--Luc, the scientifically proven self-proclaimed zen buddhist - But I could
be wrong... :o) :o) :o)

Relevant Pages

  • Re: java string encoding
    ... > unicode and use a printBytes method to display the hex value to System.out. ... This says "take the sequence of 16-bit Unicode characters living in the ... String 'cname' and convert it to a byte array using the default platform ... "convert this Java char sequence to bytes using 'BIG5' to do the conversion. ...
    (comp.lang.java.programmer)
  • Re: Unicode in SQL queries
    ... > Unicode escape sequences but rather the Unicode characters themselves. ... I would expect that you would have to use N'<some string in Chinese>', ... This is nothing which is supported by SQL Server. ...
    (microsoft.public.sqlserver.programming)
  • Re: Unicode in SQL queries
    ... > Unicode escape sequences but rather the Unicode characters themselves. ... I would expect that you would have to use N'<some string in Chinese>', ... This is nothing which is supported by SQL Server. ...
    (microsoft.public.sqlserver.odbc)
  • Re: Tranfering unicod charcters in Socket programming!
    ... You are telling about conversion b/w MBCS to Unicode. ... If this is not possible Shall I try with string to wstring ... int SendStringAsUnicode ...
    (microsoft.public.win32.programmer.networks)
  • Re: using structs like BROWSEINFO and OPENFILENAME (string members
    ... your discussion of unicode ... vs ansi reminded me to recheck my typelib and found a couple of errors. ... > is declared as string, the other is declared as long. ...
    (microsoft.public.vb.winapi)