On Tue, Dec 7, 2010 at 7:42 AM, Mads Kiilerich <m...@kiilerich.com> wrote:
> On 12/07/2010 05:16 AM, Marc-André Moreau wrote:
>
>> This is causing me some problems, because the timestamp is a 64-bit
>> little-endian integer. Does anybody has an idea on how I could compute
>> that value in a way that is going to be portable to 32-bit/64-bit +
>> little-endian/big-endian systems + various compilers? I'm a bit stuck on
>> this one.
>>
>
> We already do use int64 in rdpdr. Is it your intention replace that too?
>
No, I in fact just looked at the code from rdpdr and used an int64 in my
code. However, I'm still lacking a way to convert that value to
little-endian representation when on a big-endian system, since the protocol
needs it to be in little-endian no matter what. I need something similar to
what we have for STREAMs but that would simply output an int64 to an 8-byte
buffer in little-endian representation. I could write something inside my
method, but I'd rather make such a macro usable elsewhere for the next time
we need it.
>
> /Mads
>
------------------------------------------------------------------------------
What happens now with your Lotus Notes apps - do you make another costly
upgrade, or settle for being marooned without product support? Time to move
off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
use, and manage than apps on traditional platforms. Sign up for the Lotus
Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
_______________________________________________
Freerdp-devel mailing list
Freerdp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freerdp-devel
