Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!att!pacbell.com!ucsd!sdd.hp.com!news.cs.indiana.edu!arizona.edu!arizona!dave
From: dave@cs.arizona.edu (Dave P. Schaumann)
Newsgroups: comp.lang.c
Subject: Re: movedata ()  recoded in 80x86 assembly
Message-ID: <872@caslon.cs.arizona.edu>
Date: 15 Feb 91 03:08:56 GMT
References: <5024@umbc3.UMBC.EDU>
Distribution: usa
Organization: U of Arizona CS Dept, Tucson
Lines: 38

In article <5024@umbc3.UMBC.EDU> cs106132@umbc5.umbc.edu (cs106132) writes:
>
>   Hi,
>I was wondering if anyone out there show me an example of coding a
>routine that will do the equivalent of Turbo C's "movedata()" function.

I was going to reply to this through e-mail, but I think it is something
worth saying to the whole net.  The name of this group is "comp.lang.c",
not "comp.lang.c.ibm".  This, and a lot of other posts in this group have
little or nothing to do with the language C.

I would suggest to everyonewho is considering posting a message to comp.lang.c
to ask themselves this question:

"will anyone without a <insert name of your computer here> care about this?"

If the answer is no, please, please PLEASE don't post it here.  Somebody will
no doubt suggest I use my kill file.  Well, this is my kill file for this
group:

/:*TURBO C*/:j
/:*TurboC*/:j
/:*Quick C*/:j
/:*QuickC*/:j
/:*Microsoft C/:j

And it *still* doesn't catch all the IBM-specific noise that goes through this
group.  :(  Instead of trying to catch every permutation of IBM-ese in my kill
file, I'd like to see everyone show a little common sense in posting.  When I
have a machine-specific question, I post it to comp.sys.amiga.programmer.
Please have the courtesy to post machine-specific questions to machine-
specific groups.

Thank you.
-- 
Dave Schaumann      | DANGER: Access holes may tear easily.  Use of the access
		    | holes for lifting or carrying may result in damage to the
dave@cs.arizona.edu | carton and subsequent injury to the user.