World: r3wp

for the record (for the other people reading, which might not be 
as fluent in the more low level aspects of the core)..


I just want to note that your comment about thread safety doesn't 
only apply specifically to the /into... 


It applies to *all* series usage in REBOL 3 since they are mutable 
and MANY functions modifiy series "in-place".


Other languages always copy on assign so its not as big an issue 
as in REBOL.

Agreed. Though not many other languages always copy on assign - that's 
a relatively new habit.

Or copy on any change, rather than on assign, as Java does with String

Does anyone have a well-tested mezz version of CASE handy for use 
with older REBOL cores?

Ladislav's PIF is my first stop.

how old is old?

1.2.47

I don't know where this came from:

	case: func [
		[throw catch]
		args [block!] /local res
	] [
		either unset? first res: do/next args [
			if not empty? args [
				; invalid guard
				throw make error! [script no-arg case condition]
			]
		] [
			either first res [
				either block? first res: do/next second res [
					do first res
				] [
					; not a block
					throw make error! [
						script expect-arg case block [block!]
					]
				]
			] [
				case second do/next second res
			]
		]
	]

Thanks Graham!

looks like PIF!

That's Ladislav's PIF, just renamed.

:-)

Yep ... !

All roads lead to Ladislav.

Does anyone else experience the inability to read the clipboard ?

I can paste from the browser to notepad, and other apps, and it's 
just text, but .... the clipboard shows empty.  The problem will 
go away if I reboot though.

If I write to clipboard://, nothing is there either ...

REBOL sometimes seems to get confused if there is data on the clipboard, 
possibly related to the format of the clipboard data. Writing can 
fail at times too IME. Clearing the clipboard before writing usually 
solves the problem for me.

I think this is also what messes up AltMe's clipboard behavior at 
times.

Correction, I can write to the clipboard:// and paste into other 
apps, but Rebol is seeing nonthing there.

I can paste this: test
from Rebol, but can not paste into a new instance of View

Do you have any kind of clipboard monitoring software installed?

No, I don't

What program are you writing data to the clipboard with?

if the clipboard were screwed .... then Altme wouldn't see it either??

I was just copying from Chrome's address bar .. and also writing 
to the clipboard using core.

AltMe is built against an older core.

ok, let me raise up an old core

What OS and what REBOL version?

Ahh...... !!

fails on 
>> rebol/version
== 2.7.7.3.1

works on 
>> rebol/version
== 2.7.6.3.1

Windows 7 prof

Interesting, and very good to know.

I wonder what happened to the clipboard handling...

Only RT can say, unless a changelog is posted somewhere.

Could be as simple as a change that tried to handle errors better 
and now fails for some reason.

started up view 2.7.6, pasted to clipboard and can't read in 2.7.7 
again.

I'd better log this to rambo

Yeah, thanks for testing that.

And thanks to Ladislav for PIF/CASE.

RAMBO Ticket #-4779

Hmm, rambo only goes to 4402 for me here. Most recent doesn't show 
your ticket.

no, it's negative meaning it has not been reviewed yet

Hasn't passed Gabriele's spam filter

Ah, I missed the negative sign, and forgot that Rambo did that.

Yes, I wrote PIF, and inspired Carl to write CASE, I guess. Later 
on, I renamed PIF to CASE for compatibility. (and because CASE is 
a better name than PIF)

graham, I've been using 2.7.7 for a while and have never had any 
issues with the clipboard.   I am running xp though, so its possible 
that something in windows 7 is causing this.

It's possible, that something in REBOL causes it does not work under 
Windows 7 :-)

a lot of the APIs have changed in Windows vista/7 (not sure about 
Clipboard).  

the kind of changes I would expect...  if its not using the latest 
apis, newer features in the OS could simply be preventing REBOL from 
accessing this device.

just like how these new OS prevent you from writing within the program 
files folders.


some things which had defaults, maybe now require explicit flags... 
etc...