@developers,

I've a question regarding OVERLOAD resolution. How is the correct procedure selected ?

• based on SizeOf() ... pretty lenient way 'bitness check only' ?
• based on TypeOf() ... more restrictive way 'data-type match' ?

Other possible methods used? Thanks in advance.

Daniel Ouellette wrote:do you have a suggestion for a title ?

Suggestion:
[solved] About FBC's libraries (internal's only)

My first language is: "swiss-german" second language is: "german" (early school days task) The try to teach me "french" in school was "highly unsuccessful" trird language is: "english" fourth language (badly): "afrikaans" To close this thre...

Daniel Ouellette wrote:So, if I understand correctly, I can do whatever I want with my program made with Freebasic.

Finally, you've gotten the gist of what I've written ...
(use at least a "DISCLAIMER" in the license, to keep your rear-end safe)

Again, as simple as I can possibly make it (its pretty complex in fact): 1) FBC (as a whole product) doesn't put any licensing related restrictions towards your SW created with FBC. (FBC is simply "the tool used" to convert source to executable) 2) If you want to sell it, you'll have to ne...

Hi,

you might want to change the 'misleading' title somewhat ... (in your initial post).

Between you (your SW) and the client/customer/distributor ...
(it has absolutely nothing at all to do with FBC, or it's own licensing to you)

dodicat wrote:Would that not save a lot of hassle?

Sorry, but no it doesn't at all.
It hasn't actually ever been about fbgfx.bi but, the internal libraries, to FBC.
(whether they pose a licensing issue, or not)

Hi, from here it's going to be 'legalese' I'm afraid. ... a client showed interest in distributing what I do. since above seems to indicate a business proposal, you'll have to be careful ... The simple way whould be to sell it all to the 'distributor' and, let him/her deal with all the ugly details....

So, according to the many discussions about this, I also have to give the client the program I wrote to be within the rules and not just the compiled executable, is that correct? Not correct, there is no need to disclose the source code ... (just the executable is okay). FBC's internal libraries ar...

bfuller wrote:I had to change line 4

Code: Select all

dim as integer xres,yres

That just tells us, that your version of FBC is outdated. In the 1.08.n versions of FBC, dodicat's code works flawlessly ...

Therefore: download/install the current FBC version 1.08.1 (for your system)

InpOutx64.dll.a = in-/export library (description what a .dll contains) If you don't have one, use the: InpOutx64.dll (instead) and should it be here?: C:\FreeBasic\FreeBASIC-1.08.1-winlibs-gcc-9.3.0\lib\win64\... Yes, correct. This is just for compiling. Read my previous post again until you unders...

Put a copy of the .dll to: [FBC-Dir]\lib\win64\ folder (the compiler needs it there).
Except you have the correct .dll.a file (in-/export library).

To run the compiled .exe, the .dll should be in the same folder ...

Julcar wrote:... but after all there are just ascii chars + null, ...

While this is true for english, it may be very different for other languages, especially if
they're using different alphabet's: cyrillic, arab, hebrew, chinese, japanese, thai e.t.c.

@Julcar, why don't you get the documentation from it's source (manufacturer)? See here for: WinHttpQueryHeaders() There is also (seems to be more current): WinHttpQueryHeadersEx() Looks to me, that they both require WString Ptr, aka: StrPtr(WString) . Btw: don't understand what's apparently wrong wi...

What I've forgotten to mention, there is one exception:
if the variable is a String, then StrPtr(string_var) is mandatory.

CPtr( Any Ptr, StrPtr(string_var) )