World: r4wp

Just to clarify: Carl said it was his intention to stop by if he 
can get away from work for a bit.  I'm going to see if I can pin 
him down to a date and time.

@robert .. I made several pull requests against the R3 docs yesteday, 
see https://github.com/saphirion/documentation/pulls

Yes, thanks. I saw them. I or some of our team will check them and 
integrate them.

I hope to find some time tomorrow to look at them. Otherwise on Monday.

pair! can be floating point in R3. Is there a reason, it wasn't made 
a new datatype?

Robert, what about If someone ports those docs to REBOL Wiki ?
They would be easier to manage as DOC is not CODE.

I'd prefer them to be in the github repo

This way we only allow approved changes to be made

Graham, I don't think there could be a war on changes.
On REBOL wiki many hands could work on the documentation.

well, you may not recall but there were wholesale changes on the 
rebol.net wiki by a well intended person .. but they all had to be 
reverted

I don't people want a repeat of that experience

but the git docs could be mirrored in an unofficial community wiki 
.. but the official ones would be on the repository

Graham, I knew about this accident.

The solution we have is to revert the changes and inform the user 
as soon as we acknowledge the problen.

Just a question: do we know what has been lost during the big modification 
of REBOL wiki ? Is there a way to discover this?

For us docs stay on github. From there we integrate back into our 
mainline and make official releases. And from our mainline the docs 
on our web-site are generated.

Everyone is free to use the github as base for a wiki.

Otherwise it's unmanageable. Since there is no single point of R3 
project at the moment, it doesn't make sense to spread information 
on several places, get them out of sync etc. We need one place, where 
people know what they get.

Robert, Ladislav has sent to youa document with the changes of R3 
compared to R2. Could you upload it somewhere ?

Giuseppe: https://github.com/saphirion/documentation/blob/master/r3/whatsnew.mdp

Yes, I have just seen the ANNOUNCE group ! ;-)

So what are you asking for?

Or does that already answer your request :) ?

Andreas, I have read the REBOL3 group and wrote the request. Then 
read the ANNOUCE one and discovered the answer to my request was 
already there !

Which makedoc version should I use to compile those mdp files? I 
used makedoc2.r but the output html file is not correct completely?

makedoc-pro?

yes

Can you explai what the follwing function do?
http://rebol.informe.com/forum/rebol-3-f9/what-does-it-t65.html

Invisible

http://rebol.informe.com/forum/rebol-3-f9/what-does-it-t65.html

that function just converts a string (rebol script/code) into :C 
encoded string".  Such C-strings are then used usually at R3 boot 
time to execute all the interpreter system or host code etc.

Hi, i'm at the beginning of a project in which i need access to a 
remote MySQL db. 

I tried Softinnov's MySQL driver, but that seems to be outdated (MySQL 
complains about client protocol).
Does anyone know an up-to-date MySQL driver for Rebol (2 or 3)?

hmm, maybe R3 plus ODBC extension?

but that's most probably for Windows ...

@arie, what version of the MySQL driver are you using?

and what version of mysql?

@james_nak 1.2.1 from 12/07/2008

Arie, try with http://softinnov.org/tmp/mysql-protocol-41.r

@Maxim 5.5.31 protocol version 10

@DocKimbel i'll try ...

latest drivers should work with 5.5  IIRC

I'm definitely using v5.5.31 on windows with R2 v2.7.8.  (just checked).


 pretty sure Quarter Master uses Doc's drivers (which is what is setup 
 for mysql right now), though I may be wrong.

@DocKimbel that works; hurray!

I guess that the documentation on Softinnov's site is still appropriate?

Yes, the documentation is still up to date.

Thank you very much :-))

You're welcome. :)

Continuing from #Red group. A johnk asked for multi-line source from 
Carl. This is my W_GETS code in World, which has multi-line (blocks 
and long strings). I don't know, if you can use it, as World might 
be different internal:

char prompt_str[]	= "prin system/console/prompt";
char block_str[]	= "prin system/console/block";
char string_str[]	= "prin system/console/string";

#define W_GETS \
	if (W->line_read) { \
		free (W->line_read); \
		W->line_read = NULL; \
	} \
	if (W->top_of_series > W->series_base) { \
		W->stack = W->stack + 1; \
		int trace = W->trace; \
		W->trace = 0; \
		if (*W->top_of_series == BLOCK_BEGIN_T) { \
			tv.newline = 1; \
			do_string (W, block_str); \
			int i; \
			for (i = 0; i < W->top_of_blocks - W->blocks; i++) \
				w_printf ("    "); \
		} else { \
			do_string (W, string_str); \
			w_printf ("    "); \
		} \
		W->trace = trace; \
		W->stack = W->stack - 1; \
	} else { \
		W->top_of_code = W->code - 1; \
		W->top = -1; \
		if (NULL != W->P) \
			printf ("**** W->P != NULL ****\n"); \
		W->stack = W->stack + 1; \
		int trace = W->trace; \
		W->trace = 0; \
		do_string (W, prompt_str); \
		W->trace = trace; \
		W->stack = W->stack - 1; \
	} \
	W->line_read = w_readline (&auto_brackets, &tab_completion); \
	reset_stack (W); \
	if (W->line_read == NULL) throw_error (W, ERRMEM_S); \
	if (W->line_read[0] == KEY_CTRL_D) throw_error (W, QUIT_S); \
	W->save_line_read = W->line_read;

Some exmplanation:


W->top_of_series is a stack holding the different types of series 
being entered in the lexer, defined as:

#define BLOCK_BEGIN_T		58
#define PAREN_BEGIN_T		59
#define LONG_STRING_BEGIN_T	60
#define PATH_BEGIN_T		61
#define GET_PATH_BEGIN_T	62
#define LIT_PATH_BEGIN_T	63
#define BINARY_BEGIN_T		64
#define SET_GET_PATH_T		65


The code about trace is just, if tracing is on or off in World. W->top_of_code 
is a pointer to where the code for the virtual machine in World is 
being created, and W->code is the bottom of that stack in instructions, 
W->top the top. do_string executes a string of World code.

stack *of* instructions

The line
	tv.newline = 1;

sets a newline in the block of code entered. tv is a Tagged Value 
in World, a value with type specification.

The printf ... W->P != NULL is just some debug code, that should 
be removed.

as long as you are not inside a string you should also reagard comments