xavieraloy wrote:Can you reupload please?

Check out nettobac. It's based on the same routines as SNC, but in contrast it offers a more "BASIC-Like" API.

@fxm: We're talking about compiling against a library. Example TYPE AS LONG size_t ' correct: 'DECLARE FUNCTION memcpy CDECL LIB "c" ALIAS "memcpy"(BYVAL AS ANY PTR, BYVAL AS ANY PTR, BYVAL AS size_t) AS ANY PTR ' incorrect (name isn't present in the binary) DECLARE FUNCTION memc...

Well, sorry, but I took what you wrote literally . Taken literally, it was wrong, ... ⋅ One of us translated and provided more then 20 high-quality header sets for C libraries, even complex ones like GDA, LDE or GTK. ⋅ One of us developed several tools to auto-create FB headers ...

VANYA wrote:... the library operates with the type zstring , and I am working with binary files.

Not entirely correct: function g_pattern_match() requires the string length as mandatory parameter. This means it also searches in strings containing zero bytes.

Hi Vanya!

You didn't mention cyrillic characters in your first post.

When you're talking about a GTK-GUI, and before you add another dependency (PCRE library), you may want to check the GPattern function family.

Regards

When the raw binary data contain ASC characters, the difference between upper and lower case is bit number 5. For a case-insensitive search you can set this bit and search for lower case, or clear this bit in order to search for upper case. Using INTEGER for the conversation, you could convert 4 (32...

I would like to find a way to take the numeric elements from Date and Time and and compress them into a Long data type. Check out the C-runtime time_() function family. #INCLUDE ONCE "crt/time.bi" VAR t = time_(), g = gmtime(@t) WITH *g ?" Year: ";.tm_year + 1900 ?"...

TeeEmCee wrote:

TJF wrote:

TeeEmCee wrote:No, that's not correct.

What's incorrect?

... I assumed you meant ...

Based on an assumption you tell everybody that my entire statement is not correct? That's not quite respectable.

TeeEmCee wrote:No, that's not correct.

What's incorrect?

You talked about a compile error. I know, a message starting with ld: is comming from the linker.

And I think that we agree, that the linker couldn't bind the function named _assert.

Found the problem! The RUN statment parses the command line. When the one and only argument is the script name, it gets passed as-is execve("/bin/dash", ["/bin/dash", "/tmp/script"], [/* 28 vars */]) = 0 In contrast, the commands in the single quotes get butcher...

... but how does Linux know what 'fbc' (or 'gcc', which I just tried) is, was it part of when I did the './install.sh -i'? fbc is the name of an executable on your HDD. Linux searches all directories in $PATH to find it. You may have multiple executables called fbc in different folders. In that cas...

Thanks for the tipp!

I never used strace yet. It'll take some time to find out if it helps.

BTW: The ticks are mandatory, dash expects all commands in one argument (since further arguments may follow).

Regards

The source file examples\unicode\hello_UTF32LE.bas may have linux line endings (!"\n"), while wodniws expects !"\n\r".

I'm a bit confused, where is the path coming from, the location of the current .bas file? %d - substituted by the absolute path to the directory of the current file. %e - substituted by the name of the current file without the extension or path. %f - substituted by the name of the current file with...

Your file basic_funcs.bas contains a call to a function named _assert, but this function isn't declared.

If this function is in the library libbig_int.a, you've to DECLARE it in the FB code.