Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Pavel A. <pavel_a@xxxxxxxxxxxxxxx>
- Date: Sun, 23 Jul 2006 05:28:02 -0700
Hi Norman,
I've sent several feedbacks in past few months,
from email address not linked to my MSDN id at all -
and never received a reply like that.
Can it be that you write in a format they can't read (HTML,
or Japanese fonts etc) ?
Regards,
--PA
"Norman Diamond" wrote:
Mr. Holan, you're right, your suggestion isn't as useless as I said. For
readers who acquired Microsoft US's web site
http://msdn.microsoft.com/library inside North America instead of outside,
your company maybe treats their feedback differently. (Still not your
fault, I understand. Still your company's fault.)
"Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OfkvlwHrGHA.4120@xxxxxxxxxxxxxxxxxxxxxxx
weird, we get suggestions for improvements all the time through the link
w/out requests for support incidents
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Norman Diamond" <ndiamond@xxxxxxxxxxxxxxxx> wrote in message
news:OAfCzDHrGHA.716@xxxxxxxxxxxxxxxxxxxxxxx
The last two times I sent feedback on MSDN topics (using the link at the
bottom of the page), Microsoft responded that Microsoft US's MSDN site
(http://msdn.microsoft.com/library) had been purchased by me outside of
North America and therefore I should pay support fees to Microsoft Japan
in order to report bugs in Microsoft US's MSDN site. I did not obey.
Mr. Holan, I understand that this is not your fault, but still your
suggestion looks pretty useless.
"Doron Holan [MS]" <doronh@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OaMh2sGrGHA.3680@xxxxxxxxxxxxxxxxxxxxxxx
pls send feedback on the ddk topic so that it can get fixed (using the
link at the bottom of the page)
thx
d
--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Pavel A." <pavel_a@xxxxxxxxxxxxxxx> wrote in message
news:72CA6EFA-0DBB-4394-ADA8-61422F299341@xxxxxxxxxxxxxxxx
"usfinecats" wrote:
Dispite what the doc's say, I have observed that rtlcopymemory and
rtlcopybytes both generate the same code. This is unfortunate, as I
need to
copy an array that overlaps its destination.
--
Gak -
Finecats
Yet another copy & paste bug in documentation.
Use RtlMoveMemory.
--PA
.
- Follow-Ups:
- Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Norman Diamond
- Re: rtlcopybytes and rtlcopymemory both generate same code
- References:
- Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Doron Holan [MS]
- Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Norman Diamond
- Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Doron Holan [MS]
- Re: rtlcopybytes and rtlcopymemory both generate same code
- From: Norman Diamond
- Re: rtlcopybytes and rtlcopymemory both generate same code
- Prev by Date: Re: Address Verification
- Next by Date: NDIS IM - problems with NdisSend
- Previous by thread: Re: rtlcopybytes and rtlcopymemory both generate same code
- Next by thread: Re: rtlcopybytes and rtlcopymemory both generate same code
- Index(es):
Relevant Pages
|