World: r3wp

Of course, you could make some real headlines, and just BSD the whole 
thing.

BrianH ..doing it right might mean a wait for a long time

Carl was also suggesting releasing a license to IOS ....

No it won't take long - it's just a matter of removing the license 
code and doing a rebuild.

please, fix this 300ms delay !
  timer [call/wait "echo 1"]
1
;   0:00:00.301731
  timer [call/wait "echo 1"]
1
;   0:00:00.301543

And if it does take long, we can do it right next month and do your 
approach now.

W: in windows or Linux?

os x but geomol ryoed on linux I think a swell

ryoed -> tryied

there might be a reason why there was such delay put into REBOL?

W: I've posted the C source to Call a few times, but no one has ever 
offered any fixes.

yes i think so

Well, it is quite possible that fixes got lost-in-reply.

BrianH please? 8-)

People need to nag me more if they contribute a fix, and it gets 
lost.

BrianH .. a public license means that everyone gets ssl, odbc, oracle, 
encryption today without waiting for a new build.

I don't know though if such a license would also be usable for the 
SDK ... which Carl may not want to do .

P: there is no reason for such a delay.  But, then, the code is not 
at all simple. If you've ever seen it, you would vomit. (PS: I did 
not write it.)

:-) I do remember - over 1200 lines of code ... but at least "it 
works", and in R3 'call is almost unusable ...

300 ms is a lot of time in response time when using call/wait or 
call/output in a Cheyenne rsp. Please fix it!

So, BrianH, have you summarized the priorities in r2-beta yet ?  
:)

Is RAMBO still active? Many bugs probably there. I wonder if over 
the time (depends on how long we want to continue to maintain R2 
family of products) we should port it to CureCode?

Will, that "echo" calls a cmd.exe internal command on Windows. Might 
that be part of the delay?

I agree with Graham - R2 is so wide field, that we should move the 
project to R2-beta world, which is already well established ...

Give me a little time to go over them, I should have a list by this 
evening. I'm at work today.

timer [call/wait "print 1"]
1
;   0:00:00.301498

>> timer [call/wait "print 1"]
0:00:00.031

>> t1: now/precise call/wait "print 1" t2: now/precise print difference 
t2 t1
0:00:00.082

Using R2Beta should be fine for this week, but we need to switch 
over to using the R3 development infrastructure before the release 
next month. We won't have the time and effort available for monthly 
releases if we can't share resources. The rapid releases of R3 are 
only possible because of the R3 development infrastructure.

humm.. than the beahaviour is on nix only

release this week ....

is point #1

Yep.

Yes. And fixing the installer is one of the top priorities for this 
release.

It hasn't worked at all for the 2.7 series, and worked incorrectly 
before then.

I see a consistent 0.1 second delay in Snow Leopard.

B: Yep. Not a good thing for new users.

What about VID? IIRC, you, Anton, Henrik, were working on some resizing 
or fixes? I just hope we will not make View incompatible with existing 
scripts in the last generation of R2 productline?

fedora>> timer [call/wait "echo 1"]
1
0:00:00.304267

PS: need a better error msg for:
** User Error: Bad face in screen pane!

(happens when opening view via ssh - due to non X envr.)

Pekr, not in this release. We don't have the time to test such things. 
Once we switch to the community development infrastructure this can 
be done much easier.

Must run now, work beckons, be back later.

So, what's the verdict?  Wait first for a new build or a public license 
code release?

Graham - wait for the debate to reapper in 2012 :-)

I would hope R2 is no longer in use in 2012 ...

It will be a build. Even if just a few changes.
Must go. BBL.

2.7.7 release

Call
dockimbel:

About CALL console window issue, the CreateProcess( ) win32 call 
has flags to hide the window. There just need to be set.

In the STARTUPINFO used by CreateProcess( ), just set in dwFlags, 
the STARTF_USESHOWWINDOW flag and set wShowWindow to SW_HIDE.

maybe add a new refinement and let the users decide when they want 
to see the console window ?
or maybe just /show

Paul:
Run is not enabled

Graham

Is anyone concerned that shell windows opened in Encap do not contain 
the correct window title?
Rambo #3660 ( reported march 2005 )

Brian

For me, the big question is what kind of release we will be doing:

- 2.7.7: Patching glaring bugs in a few natives, VID fixes, and continuing 
the backports and mezzanine fixes.

- 2.8.0: Backporting some of the R3 native changes (function, not 
infrastructre), and the above.

I think that the decision a long time ago was to focus on R3 as a 
priority, and just patch up R2 as necessary.

At the very least, I would want a 2.7.7 to have a version that fixes 
post-2.7.6 mezzanine bugs, and 2.7 series regressions vs. 2.6.3.

Henrik
We also need to implement BrianH's new window resize scheme.

Ashley,Anton, Brian, etc ... VID fixes

Graham
Fixes to prot-http to support put etc.

BrianH

SQL_FLOAT and SQL_REAL are converted the same way, just with different 
sizes. And yet SQL_REAL works and SQL_FLOAT doesn't, at least with 
SQL Native Client (an ODBC 3.5 driver). Perhaps that difference can 
point you in the right direction.

Henrik
view/new make face []
a: open/binary/direct/no-wait tcp://:9000
forever [wait reduce [ a 0.001]]


This produces a 16 byte leak when started. And when I move the window 
and click in it, I get a lot of 64 byte leaks.

Will: in 2.7.7.4.2: 
>> timer [call/wait "echo 1"]
1
0:00:00.037984

This is from a change I made in the timeout period of the io pipe 
handler.

However, I am unsure of the general impact it may have.  It causes 
the io pipes to be polled 10x faster than before... which may not 
be a good thing.