home *** CD-ROM | disk | FTP | other *** search
- Path: informatik.tu-muenchen.de!fischerj
- From: fischerj@informatik.tu-muenchen.de (Juergen "Rally" Fischer)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: PPC compilers
- Date: 17 Jan 1996 17:06:01 GMT
- Organization: Technische Universitaet Muenchen, Germany
- Distribution: world
- Message-ID: <4dja9p$1vo@sunsystem5.informatik.tu-muenchen.de>
- References: <4ctghg$bq@serpens.rhein.de> <4cv5j8$dn6@sunsystem5.informatik.tu-muenchen.de> <4d0k1i$asm@serpens.rhein.de> <4d66n7$h7i@sunsystem5.informatik.tu-muenchen.de> <4ddgr1$7m3@serpens.rhein.de> <4der0t$mpj@sunsystem5.informatik.tu-muenchen.de> <4dg0o8$h87@serpens.rhein.de>
- NNTP-Posting-Host: hphalle5.informatik.tu-muenchen.de
- Originator: fischerj@hphalle5.informatik.tu-muenchen.de
-
-
- In article <4dg0o8$h87@serpens.rhein.de>, mlelstv@serpens.rhein.de (Michael van Elst) writes:
- |> fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) writes:
- |>
- |> >I knew it! I knew the only way you got is misquoting! really weak.
- |>
- |> Misquoting ? You agreed that you have problems with the english
- |> language. That's what you wrote and that's what I quoted. If you
- |> wanted to say something different then you should have written that.
-
- grrrr, you are kidding, don't you ? ;) I still hope that this is all
- done with a ":)" instead of a ":|" in mind.
-
- The original thread:
- ------------
- |> You have problems with the english language.
- |>
- |> You said that you can't see how many bytes are written in
- |>
- |> *a++ = *b++;
- |>
- |> but you can in
- |>
- |> move.w (a0)+,(a1)+
- |>
- |> And you said this was an advantage.
-
- This is true, I said in the special case I mentioned it's an advantage,
- and I stressed I only tell about this case:
-
- - debugging this line
- - having not included the type definitions in the C-case, but defined
- it buggily char * in the header.
-
- for this special case, if the routine is for example to copy an array
- to colorregisters, a move.b will hit my eyes, while in the C case I
- would maybe rather scan the instructions around for bugs.
- ------------
-
- What you made of it:
-
- ------------
- >|> You have problems with the english language.
- >|>
-
- >This is true, [...]
-
- Thanks.
- ------------
-
-
- 1) You quote only partially, to make it become different sense, with even
- cutting off the words in the _same_ line, I had lower-level-just-for-fun
- flames with other dudes, but until now I met nobody who did quote as
- uncorrect as you!
-
- 2) You quote my reply to a different claim of you, this is not ok.
- My answer "this is true" was done to "you said this was an advantage",
- but stressing I did claim this only for my very special example.
-
-
- I really don't know if you are
-
- a) Just doing this intuitive, not recognizing it.
-
- b) Just going the clever way, handling all with this behaviour,
- incorrect but doesn't provide much trouble to you, rather the
- opposite, you can get a good politician with it.
-
- The thought that it could be b) makes me angry, as .programmer is
- not a place to train this behaviour but a place to help each other.
-
- |>
- |> >"This is true, I said in the special case I mentioned it's an advantage,..."
- |>
- |> I am wondering why you don't try to give OCC-sources as examples
- |> why assembler is soooo much more readable.
-
- If I translate this into "your special example is non-real-world so it
- doesn't care in C-programming", I agree. No tricks needed ;)
-
- |>
- |> >: *colorregptr++ = *colormapptr++;
- |> >hmm your variablenames got more letters, the only difference to my example :)
- |>
- |> Yes. That's why you do not see the difference. With a name of 'p' I
- |> might need to look up its declaration. With a name of colorregptr I
- |> am quite sure that it is defined to point to a color register. No ?
-
- yes. (Now don't cut off ;) I already admited it would have to be a own
- definition, done inidividually for that loop rather than a fix include
- definition usable global for all Amiga implemenations. I know that if
- it's done like in _your_ example, then it's all easy.
-
- |>
- |> >I'm too lazy to look this up now, it obviously is also a unfair misquote.
- |>
- |> Unfair ? Is it unfair to make you read your own statements ?
-
- a) or b) ... mhmhm... :\
-
- |>
- |> >If I puzzled something from your words together, I could get something like:
- |> >Michael van Elst writes:
- |> >> I am a 'c00l c0d3r', nobodys hacks are cO0l3r than my trackloaded
- |> >> A500 Kick V1.2 only intros.
- |>
- |> Which is an obvious invention of yours. I am just quoting what you
- |> write. I do not puzzle words together. I do not even quote out of
- |> context.
-
- Well, the 1st/2nd sentence, true, but the last one, I don't agree!
-
- |>
- |> --
- |> Michael van Elst
- |>
- |> Internet: mlelstv@serpens.rhein.de
- |> "A potential Snark may lurk in every tree."
- ------------------------------------------------------------------------
- fischerj@Informatik.TU-Muenchen.DE (Juergen "Rally" Fischer) =:)
-
-