Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - luke

Pages: 1 [2]
16
QB64 Discussion / One final update for 2018: new gcc
« on: December 30, 2018, 11:36:21 pm »
The development build now comes with gcc 8.1.0 on Windows, which is a refreshing change from  whatever god-awful version it was using before (hint: I don't think it'd been updated since 2012 or so). If you have C++ compilation errors post them here and I'll sort things out quick smart.

Early next year we'll probably see an official 64 bit download appearing for Windows, based on Steve's work. Most people are probably using 64 bit machines these days but rest assured, the 32 bit version won't be going anywhere.

There's also the matter of Linux binaries not being launchable from some new file managers - that'll get some love soon, too.

We have variable length strings in UDT's now but don't hold your breath for arrays in there as well.

17
QB64 Discussion / Variable-length strings in TYPEs
« on: October 23, 2018, 06:47:31 am »
Q: How long is a piece of string?
A: As long as it needs to be.

Soon you'll be able to do something like this:
Code: QB64: [Select]
  2.     a AS INTEGER
  3.     b AS STRING
  5.  
  6. DIM a as t
  7. DIM b(20) AS t
  8.  
That is, you'll be able to have strings of variable length inside a TYPE, and have arrays of them and do all the usual stuff you'd expect with TYPE's. However, GET and PUT (as in to write to a binary file) don't natively make sense, because they rely on knowing how many bytes makes up the TYPE - now they are variable in size.So, should we:
 - Disallow using GET/PUT to a binary file with these variable length TYPE's?
 - Also write out length information that allows the data to be read back in correctly?
 - Something else?

I'm open to ideas.

18
QB64 Discussion / Continuing on from the "test the release candidate" thread on .net
« on: October 22, 2017, 11:44:34 am »
The bug relating to multiple sounds not playing properly should now be fixed. I'll look into the_SNDRAW matters soon, but I can't promise anything there - the code behind sndraw is sufficiently messy that I don't fully understand what it's doing yet.

As for C++ compilation errors, we're looking at adding some logging to make it more practical to investigate such matters. Hopefully this should be ready in time, but there seems to be some issues with it on windows XP.

Pages: 1 [2]