r3wp [groups: 83 posts: 189283]
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

World: r3wp

[Red] Red language group

Kaj
23-Jun-2011
[2496]
If you want the function to return a logic! status and a result to 
be able to handle it locally, the result needs to fetched through 
a pointer, which also raises complexity. We can't handle addresses 
very well yet, either, because get-words only work for native functions
Dockimbel
23-Jun-2011
[2497x2]
My point was: don't return a logic! statut from functions like RECEIVE, 
rather set a flag and check it after RECEIVE call.
statut => status
Kaj
23-Jun-2011
[2499x2]
RECEIVE doesn't return logic?
That rewrite doesn't work. It mixes up successful and unsuccessful 
receiving
Dockimbel
23-Jun-2011
[2501]
Yeah right, I was confused by your will to return a logic!.
Kaj
23-Jun-2011
[2502x5]
I'm flexible. :-) Not everything returns logic, only the cases that 
can
I'll just rewrite it in EITHERs for now. I'm just noting that it 
can be made very nicely REBOL like to distinguish Red/System from 
C
By the way, 0MQ is not a network communication library per se. It 
can do messaging equally well between processes and even threads, 
so wrapper performance is significant
x: does []
either true [x] [x]
*** Compiler Internal Error: Script Error : equal-types? expected 
type1 argument of type: word
*** Where: comp-either 
*** Near:  [last-type: either equal-types? t-true t-false]
Dockimbel
23-Jun-2011
[2507]
Regression from a recent change, you should get a compilation error 
saying that x is missing a return value.
Kaj
23-Jun-2011
[2508x2]
In this case, I don't need EITHER to return a value
The crash is on the EITHER not on the DOES
Dockimbel
23-Jun-2011
[2510x2]
Ok, so sounds like a check that shouldn't happen in such case.
Could you post this error (and future others) to github's tracker 
please? It is easier for me to manage them there.
Kaj
23-Jun-2011
[2512]
I won't like loosing the comfort of AltME, but I'll try
Dockimbel
23-Jun-2011
[2513]
Thanks.
Kaj
23-Jun-2011
[2514]
I've put it in there, but I won't be able to follow the discussion 
much
Dockimbel
23-Jun-2011
[2515x2]
It is more a matter of tracking than discussing.
It is also easier for others to follow current issues publicly.
Kaj
23-Jun-2011
[2517]
I understand; it's just a rotten situation that the communication 
isn't integrated
Dockimbel
23-Jun-2011
[2518]
We have #red-lang on Freenode for that. ;-)
Kaj
23-Jun-2011
[2519]
I don't do IRC, either. It's not integrated, just more fragmentation
PeterWood
23-Jun-2011
[2520]
What is AltME integrated with?
Kaj
23-Jun-2011
[2521x2]
The REBOL community?
Boron is using all the right open source buzz words, except AltME, 
and look what traction it got
PeterWood
23-Jun-2011
[2523]
I'm not sure that you can associate Boron's lack of popularity with 
the fact that Karl does not use AltME.
Kaj
23-Jun-2011
[2524]
Maybe, but I can associate my misgivings with communication systems 
that make you jump through hoops
PeterWood
23-Jun-2011
[2525]
Do you mean the Boron mailing list?
Kaj
23-Jun-2011
[2526x5]
Mailing lists are among the worst, yes
Ah, the unintegratedness begins. When I type >> in GitHub to denote 
a REBOL result prompt, it interprets it as indent markup
If you had told me twenty years ago that I would be writing prose 
such as "Local logic! in prin-int leaks as global function!", I would 
have seen it as a sure sign of dementia
I implemented error checking in the 0MQ examples. It has revealed 
three bugs in Red
It has exploded the code, though. It's quite ugly and inefficient
Gregg
23-Jun-2011
[2531]
Keep up the good work Kaj!
Kaj
23-Jun-2011
[2532]
Thanks, I intend to
GrahamC
24-Jun-2011
[2533]
Karl has failed to engage with the Rebol community as far as I can 
see.
Dockimbel
24-Jun-2011
[2534]
Kaj: thanks for the reports. I was aware of NOT issue and already 
encountered the local name clash, but never got the time to isolate 
it. Fixing them now, before going beta, is a good timing.
Pekr
24-Jun-2011
[2535]
So we are going beta soon? :-)
Dockimbel
24-Jun-2011
[2536x2]
Red/System will go beta as soon as I:
- fix the remaining bugs from the tracker,

- decide on 2 last syntax issues discussed on the ML (concerning 
struct/pointer literal syntax and aliases)
- make a pass on the specification to fix/update/complete it.
It could happen today, but I will be probably too busy with other 
non-Red tasks.
Pekr
24-Jun-2011
[2538]
And then? RED language implementation, generating Red/System code? 
That will actually mean reimplementing all REBOL natives - how long 
do you expect it to take to get to an alpha? One year? More?
Dockimbel
24-Jun-2011
[2539x2]
The next step will be working on Red memory manager, then Red compiler 
(including reimplementing all the base natives). Alpha should be 
available around September, 1st.
Yes, I should take the Red->Red/System compilation road.
Pekr
24-Jun-2011
[2541]
September 1st for the compiler, right? Not the whole REBOL reimplementation? 
You can't be so fast :-) And if you are fast, you should rename to 
SupaRED :-)
Dockimbel
24-Jun-2011
[2542x3]
I said "base natives", so not a whole REBOL reimplementation.
I will detail the milestones on red-lang.org just after the beta 
announcement.
Peter, the %function-test.reds script is missing from your last commit.
PeterWood
24-Jun-2011
[2545]
It seems to be there : https://github.com/dockimbel/Red/blob/58afdfbf99699c7bcd3f57231edae9c495e00f99/red-system/tests/source/function-test.reds