World: r4wp

ok. The same solution was made for adding time or now you provided 
earlier. Somehow the timer has to be read using a standard C library.

Yes, if you don't want to write a lot of different code for different 
operating system kernels

One day I will understand and make the video ;-)

Koel :-)

Having to add all #include for many of these kind of common functionality 
(time random i/o etc) is less friendly than having these integrated.

Sure, that's why they're in separate repositories. When Red takes 
the pieces it needs, it won't be bothered by the full bindings, but 
they can still be used in Red/System programs

In the meantime, if you want everything included, use the interpreter 
builds

'make-c-string is my friend. My Red/System scripts are so much happier 
now that I'm not assigning c-strings to arbitrary locations in memory 
like I was doing with 'as-c-string. :-)

:-) Note that most of your string initialisations were unneeded. 
Several allocations are done by the functions you're calling

How do I know when to initialize a string or not?  I was just going 
to ask that question.  Take this function from ANSI.reds for example:

	append-string: "strcat" [				"Append string."
		target			[c-string!]
		source			[c-string!]
		return:			[c-string!]
	]

Can I just do this?

file1: make-c-string 128
file2: make-c-string 128
file1: "to-process/"
file2: "dir/"
append-string file1 file2
append-string file1 "file.txt"

I'm trying to track down an access violation.

You're allocating both file1 and file2 double there. The two 128 
byte strings immediately leak away when you assign the literals

OK.  So 'make-c-string isn't really needed?  Isn't it like Rebol 
where if you don't do:

	copy "to-process/"


that you will be linking to a static memory location with "to-process/" 
in it?

linking = pointing

Then when you append to file1, you're overwriting the string literal 
inside the executable, so you're destroying your program in memory

So how would you write the above?

Allocations are very much needed, but once made, you have to guard 
them like your most precious posession :-)

The problem is exactly that you're not doing the COPY of the literal. 
Very much like REBOL

Is this the right way?

file1: make-c-string 128
file2: make-c-string 128
copy-string file1 "to-process/"
copy-string file2 "dir/"
append-string file1 file2
append-string file1 "file.txt"

Yep

I'm assuming that 'append-string copies the source parameter.  Right?

Yes, it needs to for appending. It's not a linked list of strings 
or something like that

OK.  The mental picture grows clearer.

So file2 is unneeded in there, because appending the literal copies 
it, anyway

It's a contiguous memory area, just like a block in REBOL

OK.

append-string returns the result, so you can chain them just like 
in REBOL

append-string append-string file1 "dir/" "file.txt"

If 'file1 is initialized but hasn't been assigned a value, can append-string 
use it as the target?

How do you mean? Initialising means assigning a value

What I mean is this:

file1: make-c-string 128
append-string append-string file1 "dir/" "file.txt"

But you did assign a value there: a memory block of 128 bytes

The only problem with using it as a target is that it may not be 
initialised as an empty string. For that, it needs to hold a null 
byte marker

In my tests, it did not work.  How do I initialize it with a null 
byte marker?  Like this?

file1: make-c-string 128
file1: #"^(00)"
append-string append-string file1 "dir/" "file.txt"

file1/1: #"^(00)"

There is also a pre-defined constant "null-byte" available:

file1/1: null-byte

Oh no!  Just found a bug in the Linux-ARM version of Red/System. 
 It has to do with string handling, but I haven't isolated yet.  
Will post here once I do.

If you're lucky, it may be fixed in the dyn-lib-emitter branch

It appears to have something to do with pointers and 'append-string.

Consider the following code snippet:

	print-line file1
	append-string file1 "/img00.bin"
	print-line file1

On Windows, it outputs:

	to-process/2013-06-29-20-18-55.h264
	to-process/2013-06-29-20-18-55.h264/img00.bin

The exact same code on Linux-ARM outputs:

	to-process/2013-06-29-20-19-06.h264
	/img00.bin/2013-06-29-20-19-06.h264

Odd. The append somehow considers the string empty on ARM, but it 
doesn't close the appended part with a null byte, either

That's what I was thinking.

Could you print the string lengths, as well?

How does one do that?

length? file1

That's too much like Rebol.

We could distort it :-)

The append is done by the C library, so if it doesn't append a null 
byte, that would explain it

OK.  That's just weird.  With the following code snippet:

	print-line [file1 " " length? file1]
	append-string file1 "/img00.bin"
	print-line [file1 " " length? file1]

We get these results on Linux-ARM:

	 36process/2013-06-29-20-18-55.h264
	/img00.bin 4613-06-29-20-18-55.h264

It looks like the problem is happening before the 'append-string.