AltME groups: search

Jaime thanks for asking...But there's not a simple answer.

The point I am about to make applies to any proposed variant in ORCA 
vs REBOL.


The problem with changing fundamental behaviour is that it makes 
it hard to port applications: think a few years ahead when ORCA is 
a fully operational REBOL clone, and (as an example) (unlike REBOL) 
runs on PDAs. I'd like to use ORCA so I can run an application in 
a PDA; but I want to use REBOL for all my other platforms. And I 
don't want to have to pick through code and/or support two source 
versions because of avoidable differences in behaviour.


On the other hand, an ORCA-only application might benefit from the 
"more correct" implementations of basic operations.


One possible way to square that circle is to have a set compatibility 
flag:
    system/orca/xor: false  ;; gets me REBOL XOR behaviour

I just have to wrap that in an 'attempt and I can keep a common source 
that will run under either.


[I appreciate that there may be performance issues doing it that 
way -- may be better to have compatibly options specified in an orca.r 
file that is only processed at start-up....I'll leave the details 
to the people doing the design]

Jaime, an advantage to OpenRebol is that we don't have to go through 
changing all the code that looks like this:

#define orResult(t,v) \
    orSetTF(a1, t); \
    a1->index = v;

#define orResultCopy(v)     orCopyV(a1,v)

#define orResultSeries(t,w,idx) \
    orSetTF(a1, t); \
    orSetSeries(a1,w,idx)

#define orResultSTRING(i)   orResultSeries(OT_STRING,i,0)
#define orResultFILE(i)     orResultSeries(OT_FILE,i,0)
#define orResultBLOCK(i)    orResultSeries(OT_BLOCK,i,0)
#define orResultBINARY(i)   orResultSeries(OT_BINARY,i,0)
#define orResultNONE        orResult(OT_NONE,0)

Right  now I'm very excited to be playing with a working open source 
REBOL implementation in Windows :) I wonder what dependencies it 
has, and if it can be compiled to run on Windows Phone or any other 
potentially useful operating systems.  Even just for simple file 
managment and text processing, it would be really cool to see this 
running somewhere where real REBOL isn't currently available.  And 
since it's open source, there's potential to expand it's capabilities.

Has anyone a project file for Codeblocks and Boron under Windows 
or some hints how to do it?

sqlab: you can have cmake generate a codeblocks project file for 
you

I just tried:

do to-rebol-file "L:\some\path\here\test.r"


and everything went OK, Win Vista here. Console is being launched 
form the shortcut on start bar, pointing to renamed to rebol.exe

In win.h include file in LCC compiler;
typedef int BOOL;
typedef unsigned char BOOLEAN;

That's a pity, because Jaromil requested slider and file selector 
widgets from me. When he has those, he can start using Red for a 
GUI for his Tomb security tool

Anyone have experience using Vincent Ecuyer's "rewbzip.r" from the 
script library? 

I'm having trouble unzipping a very large db file (150+ megs). It 
works for smaller zips...anyone know if there is a limit on file 
size?

Same result from cmd or clicking on file icon or Git/Mingw32

You can use -v 6 and echo all output to a file and use a text editor 
to review the output for your code.

I put alla files in red-system/tests, including Red-48x48.png. I 
got GTK-widgets.reds running, but with "Window: skipping missing 
icon.". Where do I put the PNG? As far as I see there is no path 
defined for this file in GTK-widgets.reds. Using Win7 (x64). I thought 
the icon would be built in the exe. I tried now to put the PNG in 
the same dir as the built exe and the icon shows, but I still got 
that DOS terminal to open. Sorry for stupid newbie questions.

The icon file should go in the directory where you start the executable 
from, so usually that would be the builds/ directory that Red creates 
within itself

By the way, I added an extra error message when the icon file cannot 
be loaded

Float support so far:

---
Red/System [ ]

#import [
	LIBC-file cdecl [
		cos: "cos" [
			x 		[float!]
			return: [float!]
		]
	]
]

pi: 3.14159265358979
printf ["%.14f" cos pi]
---

outputs: -1.00000000000000

#import [
	LIBC-file cdecl [
		quit-return: "exit" [  ; Exit program, returning status code.
			status		[integer!]
		]
	]
]

yes.. just found it in C lib as well... goot to know I can use the 
quit without it - I was missing the return code

Oldes: I've emailed a skeleton test file for enum to you.

I removed run-test.r as it was becoming difficult to get working 
once we needed to have tests not only in the red-system/tests dir. 
(I now use a script in another language which seems to be more flexible 
in it's file path handling.)

I've emailed a copy of the run-test.r to Oldes.


I'll take another look at getting run-test.r to run a test from any 
directory. If I can I'll restore it, if not I'll chane the docs.

well, I am bothering you here more, than if I would upload somewhere 
a project file with all sources. The app is really small, but I might 
be missing some obvious setting or something else :-)

Since compilation of included file is done everytime, and for IMPORT/DEPENDENCIES 
it is done once, and then a compiled version of a dependency is used 
everytime, which is infinite orders of magnitude faster.

I.e. after each #define and after it the #include, we would need 
to recompile the included file. That's enourmous lossage of time 
and resources.

Sorry, wrong cut and paste. The first error was:

Compiling led/led.reds ...
Script: "Red/System IA-32 code emitter" (none)

*** Compilation Error: return type missing in function: led-set-language
*** in file: %led/led.reds
*** at line: 87
*** near: [led-set-language 3 lf]

just a note - solved the ledctrl problem. I noticed it generated 
system.con configuration file, but this file was just 210 bytes. 
So I copied over the larger one from real set-up, and those affected 
functions started to work. Tomorrow I will try directly with the 
ledscreen. So, although the library is said to be C++ only, it now 
works even from R2.

so no chance to compile something like:
#enum colors [red blue] ;in file 1
#enum tests [red green] ;in file 2

compiler fails when including both file.

Can you make a red global var..
 No, we cannot.
document fixed
, still we cannot compile the examples on Windows,
because of "redeclaration of c" in win32.reds file.

the problem is, that now it throws this error if C is used in enum:
*** Compilation Error: type mismatch on setting path: char/1
*** expected: [byte!]
*** found: [integer!]
*** in file: %runtime/utils.reds
*** in function: prin-byte
*** at line: 29
*** near: [
    char/1: c
    prin char
    c

Forget it- it is, I was modifying the autogenerated file.

Then it should indeed be in the C library binding, but probably in 
the main file, because I will also move a few other functions there 
that use floating point

This code will cause an access violation as clock in libc returns 
an integer not a pointer to an integer.

pi: declare pointer! [integer!] 
#import [
	LIBC-FILE cdecl [
	  read-cpu-clock: "clock" [
	    return:    [pointer! [integer!]]
	  ]
    ]
]
pi: read-cpu-clock
pi/value

Well, Topaz compiles to or is interpreted in JavaScript at the moment. 
There are several ways to run JS on Windows outside of web browsers 
- it is one of the ActiveScripting languages, so you can use cscript, 
for instance - or you can load the Topaz environment in a web page, 
which can be a local html file with no web server needed. None of 
this is tested yet, of course, so be sure to tell us how well that 
works for you :)

I thought you could simply type the name of the file. :-)

:) Look at the bottom of the %cortex.w file. You'll see the test 
function and the m function. I just include them for now, because 
I call those two scripts all the time.

You should add link to the world page into the readme file.

Ok, under Windows, I found, I had to initialize the networking, so 
that's done at startup. (This isn't necessary under OS X and Linux.) 
You can see the code being executed in the function init_net () in 
the file src/host/win32/network.c. If you think, it should be done 
otherwise, let me know.

The file is found at
https://github.com/Geomol/World
if that wasn't clear.

My first experience with LLVM.


I tried to compile World with llvm-g++ under OS X. When compiling 
with gcc, I normally use -O2 option. I compared performance with 
the Mandelbrot test. Between compilations, I deleted all .o files 
and executable, so new compile started from scratch.

Compiling with llvm-g++:

With -O2 option, file size grow to 105% and execution time extend 
to 105% (slower).

With -O3 option, file size grow to 106% and execution time is the 
same.

With -O4 option (also Link Time Optimization), file size extend to 
122% and execution time grow to 107% (slower).


Then I tried to compile with gcc and -O3 option. Now file size grow 
to 105% and execution time shortened to 85% (faster).

Has anyone had similar experience with LLVM?

World should accept REBOL [] as header to run R2, R3 scripts through 
it without editing these.

For now, it's possible to run REBOL scripts with this function:
do-rebol: func [file][do skip load file 2]

Or when you want to put documentation before the header, or embed 
the script in a block in another type of file.

my only suggestion for structures...  make it so the semantics are 
exactly the same as C.    
i.e. you take a C header file, and do:

replace/all header-string "{" "["  
replace/all header-string "}" "]"  
replace/all header-string "char *" "pointer"
...


and basically you've got your simplest World version of the spec 
 ;-)

Gregg wrote in group #Red: "World has similar goals I believe."


Yes. To clarify: There is World and there is World/Cortex. World 
is written in C and the Cortex extension is written in World. It's 
a design goal to have as little as possible in the C part, but because 
it's also a goal to have good performance, especially with math stuff, 
some functions are native (written in C), which could have been mezzanines 
(written in World), like ABS, COS, SIN, TAN (all small functions 
in C).


But large functions like PARSE and SORT and many other functions 
are part of the Cortex extension, so they're written in World and 
is therefore open source.


With the good support for dynamic loaded libraries, good performace 
with heavier functions can be achieved that way.


And then there is the REBOL extension (in the World file %rebol.w), 
which is there to hold further extensions and definitions needed 
to run REBOL scripts. Those are not in the Cortex extension, because 
I disagree with some of the REBOL design decisions, and because I 
would like the Cortex extension not to be too large.


For me, World and Cortex has the higher priority, the REBOL extension 
the lower priority, meaning I use more time on finishing World/Cortex 
for now.

if you mean value-syntax... actually no it doesn't  :-)   but this 
does (in current implementation of file)

rebol-syntax: [
	some [
		comment-syntax
		| value-syntax
		| whitespace
	]
]

you can use 2 forms for file! :
in R2
- %"*"  quoted sting file, with ^ escape notation allowed
- %*  Form  with %ff escape notation allowed  
in R3
- quoted string file works fine

- in the %* form, the % escape notation works fine but the ^ char 
mess up  things in some cases without issuing an error

yeah, its surely some left over copy/paste code from the string loader, 
left in the file loader by error.

file-char: complement union charset {%:@} termination-char
file-char/#"/": true	;** #"/" added
file-syntax: [
	#"%" [
		quoted-string
		| any [file-char | escape-uri] ;** fail on ^ char
	] termination
]
alternative-syntax R2 file-syntax: [
	#"%" [
		quoted-string
		| some [file-char | escape-uri | #"^^"]  ;** ^ valid char
	] termination
]