PureBasic Forums - English

Thanks for this..

I'm in the UK, where the current timezone is the same as UTC, so the snippet you posted returns three identical timestamps. I'm guessing you get different results with #PB_Compiler_Date matching the local timestamp?

Quick question as per the subject line - is the date returned by #PB_Compiler_Date in UTC or local time?

Hi all,

Nice to see Windows arm64 support appear!

Is there any prospect of cross-compilation support for this, in either direction (i.e. building arm64 binaries from an x64 platform, or x64 binaries from an arm64 platform)?

i.e. any way to have both x64 and arm64 binaries produced from a single ...

Fred wrote: Wed Jun 12, 2024 12:47 pmIt's planned

Cheers!

Sorry - didn't find that thread earlier.

But it's also from 2022, and things have maybe moved on a bit now. We're starting to see ARM-based devices appearing as part of the standard range from some manufacturers now. So it's not mainstream quite yet, but it's getting close.

Obviously there will be ...

Hi,

Sorry if this has been asked before - I can't see it in the search, but it's not the easiest thing to search on...

If I understand correctly, we now have ARM support for Macs, and for Raspberry Pi devices, but not Windows. With a number of manufacturers offering Windows on ARM as a more ...

This isn't data for the threaded app itself. It's with regard to a proc in a library that might be used by threaded or unthreaded apps, and which currently has a variable declared as static. My thinking is that this is not threadsafe, and so it needs to do it some other way.

Nic's answer seems to ...

Quick question - if I have a variable defined as static, it appears that it is similar to a global variable, in that it has the same value in all threads.

Is there a way to declare a variable that is like static (local to the procedure), but has a separate value per-thread?

Declaring it threaded ...

Hi all,

I have a project that includes a couple of libraries via IncludeFile. Both of these libraries happen to need functions (not the same functions) from a particular DLL, and so both are setting up prototypes and calling OpenLibrary() to get functions from that DLL.

This means that OpenLibrary ...

My guess is it's due to the LZMA storing the file date metadata. This metadata contains an 'accessed date' field, which will change every time you add the file & could therefore be compressing slightly differently each time a second ticks past.


I think this is probably the answer, as this seems ...

Hi all,

I have code that, amongst other things, creates a pack file (with UseLZMAPacker()), and I noticed that with 6.10, the size of the resulting pack file does not seem to be deterministic. That is, I can run the same code multiple times against the same files, and get slightly different sized ...

Thanks for this - it's what I was suspecting...

So for now, if you want the UTC date, the API is the only reliable way to get it, I think.

In practice I was going to put this code back to using the API because I have existing code rolled out to quite a few PCs and existing timestamps in indexes ...

OK, here's some actual code demonstrating the differences I see (there are more than I thought). For this to work, you need two files, one with a date inside the daylight savings period, one outside. I have these, as seen from a command prompt in windows:

Directory of C:\temp

16/04/2024 10:37 2 ...

Hi
Maybe GetFileTime_() will do the job
https://www.purebasic.fr/english/viewtopic.php?t=71078&hilit=getfiletime


Yes, that's the Win32 API way of doing it, and essentially what I was doing earlier (and provides a way to get the timestamp before it gets converted into the local timezone). I ...

Hi,

I've been trying to move all my stuff over to 6.10, and part of that means doing away with separate libraries for things that can now be done natively. Previously I had a dedicated function for getting the UTC timestamp of a file using windows API calls (based on the date64 library). In 610, we ...