World: r3wp

Oh well, now that there is an official (alpha) release of rebcode, 
I submitted my HERE directive to RAMBO.

But Carl said once, a good jit like ADE would take him a month. Now 
if we can put him that long on vacation.. :))

BrainH: use RT Q & A group here, that might be faster :-)

hmm, but most of that stuff is several times the size of rebol itself 
:-)

Jump on Gabriele when he shows up..

Isn't there really a stuff like 40KB, free, crossplatform, so that 
we could have it "onboard"? :-)

I tried that. It only worked with things they were already working 
on. Gabriele and my sleep schedules have very little overlap :(

IIRC tcc is around 100, but with c-parseron board.

Pekr, that would mean Forth :)

BrianH: if HERE is really important, then I suggest you to use even 
more drastic methods to get Gabriele's attention, like telling him 
Pizza and Spaggeti don't come from Italy and that Italy can't play 
decent football :-))

I've never seen an Italian try to play football. Oh, do you mean 
soccer? :)

yes, soccer, they are quite good in it :-)

Never been to Italy (that includes DevCon2005, darnit), so I'll take 
your word for it.

BrianH - where're you from?

Chicago, Illinois, USA

Spaggethi not from italy? MAybe this helps arguing? http://science.slashdot.org/article.pl?sid=05/10/15/022201&tid=14
:)

that's quite far away from here :-) But isn't it close to Sassneranch? 
Maybe you could visit Carl to talk to him personally :-)

Ah, but proper pizza is from Chicago :)

:-)

That's more than a thousand miles away. Not a quick jaunt.

Mapquest say that just to get to their zip code, it would take 31 
hours 55 minutes in time, 2194 miles in distance.

i already asked Carl about HERE. he hasn't aswered yet, but that 
does not mean he won't.

In rebcode, testing not x, before ==> after:
true  ==> false
false  ==> true
none  ==> none  (three-valued logic, SQL here we come)
1  ==> 0  (bitwise)
1.0  ==> 1.0  (unchanged)
a

  ==> REBOL goes away without warning (where's that type inferencer?)

Thanks Gabriele! I wasn't meaning to be a jerk - I meant it about 
Carl being busy :(

Now you have a nice RAMBO entry to work with.

indeed, i was referring to Petr's message, rather than yours. :-)

Well, I think putting an entry in the Rebol Enhancements group or 
in RAMBO beats drivinf 2194 miles :)

What did Carl mean about rebcode modifying memory? I'm a little worried 
about these use-an-opcode-wrong, REBOL-goes-away errors.

That  NOT x  crash can be worked around by doing a  SETT x GETT x 
 to make sure the value is compatible.

That or be extra careful with specifying those argument types to 
rebcode functions.

you should always specify argument types for REBCODE functions...

and... use the TYPE? opcode when you cannot determine the type in 
advance.

anyway... i think there's still a lot to improve in this area...

I would prefer opcodes to just don't do anything when given bad arguments, 
instead of crash REBOL with a core dump, as a general rule.

You all have been improving rebcode greatly in that respect so far.

Carl mentioned everything is traded for speed.

Btw speed, little benchmark rebol, rebcode, c: http://polly.rebol.it/test/test/rebcode/download.r

They'll never get REBOL secure if you can cause core dumps with rebcode.

Maybe rebcode is not enabled then, or there are two different interpreters.

Core dumps on Windows are caused by unintentional buffer overflows 
and such. If you can cause them unintentionally, you can cause them 
intentionally.

There are some things you shouldn't trade for speed.

Personally i agree. OTOH lots of other apps do that trade too.

If you want to do multimedia, either trade or have a very smart compiler.

and the rebcode-portions should be a small part of the programm. 
And i guess often generated by dialects. which will add checks on 
their own, which is why we have this range-checks now (IMO)

Well yes, I want to make a very smart compiler as much as the next 
guy, but still I like the invalid-as-noop behavior that many of these 
opcodes have, that all of them should have.

At least invalid-as-error would do, rather than invalid-as-crash.

Heck, in debug mode I would like all of the opcodes to act as invalid-as-error.

hmm.. does IF work?

r: rebcode [] [
  set a -1
  lt a 0
  either [return a][return 0]
] ; works

r: rebcode [] [
  set a -1
  lt a 0
  if [return a]
] ; syntax error

ift, iff (it-true, if-false)

(why not if, unless?)