World: r3wp

If you reread the above, you´ll see that I reported more bugs than 
this issue on WINE

I´ve been muddling through bugs all night

In any case, by your own admission, you´re the wrong people to talk 
to

that's correct.

BTW, this is probably not common knowledge, but R3 does not officially 
support Win95/98/ME, even if it may run there. I don't know if that 
may have any effect on Wine behavior.

I like the current dir? function in R3.  I think it works well.

We just need to understand how it operates in R3.  It's more of an 
adjustment in our thinking than a problem.

Is it normal in R3 to get a bunch of output in the console when saving 
a file?  save %blah "test"

yes, that is for two reasons. when saving a file, a port is returned, 
which was not the case before. the other reason is that objects are 
now returned to the console.

Ok, just wanted to make sure.  That helps.  Thanks Henrik.

Switching from AltME to RebDev chat has been very hard for me and 
since I am not a core developer I will be in read only mode until 
the GUI version will be released.

However I am not negative about how things are going. We finally 
have a pubblic alpha. an upgrade mechanism, an internal chat system. 
GUI is going to be developed and also documentation reviewed.

We already have GUI in R3 but you gotta load it first via load-gui. 
 I know it is still in development though.

Yes Paul I know but it is not complete and Henrik will be back to 
work on it in march.

It will be the foundation for the RebDev GUI side.
Everyone seems now in the same cavern where Carl retired himself.

Oh, I didn't know he was the only one working on it.

I'm not a fan of rebdev either but I view it as the catalyst for 
the GUI side of it.

I suppose both Carl and Henrik ar working on it while Cyphre will 
be back soon to fix some lower level issues.

Well the good thing is that I see lots of activity on R3.

Let's count our blessings here.   At least it is active.

However we are in the middle of a big change. Once the new messaging 
system and the GUI will be complete the whole speed of REBOL3 will 
shift up again.

I think Carl is very excited about things right now and motivated 
towards getting R3 fixed, stable, enhanced, and released.

Expect a 2 months where everyone involved will work in the cavern 
with Carl and then we will finally have something to start with seriously.

March is fine for me.  About that time I really expect my project 
to be in a mature state via 2.7.6 and can then hopefully begin porting 
at that time.

By now, we could only try to test REBOL3 and report bugs in CureCode. 
It is still a big thing.

For discussion with the development team we need to use the chat 
system as everything else (AltME) seems abandoned.

My project still have everything they need in REBOL2. SQLLite, REBGUI 
and REBOL Itself.
When things will be mature I'll start to port my projects to R3.

Lets not forget it is a complete new beginning. While R2 is a mature 
man R3 is still an infant.

It is nice to see lot of interest around it. This mean that the child 
will be well supported by an extended family of relatives ;-)

Kaj, please report bugs in CureCode. And here if you like, but the 
important place to report them is in CureCode. If you have problems 
making an account on CureCode say so here or in the !CureCode group. 
Please mention that you are running on WINE in the bug, in case your 
bug is WINE-specific. We have no problems with supporting REBOL properly 
on WINE, but at least I can't test it since I am running Windows.

It is easy to report bugs in CureCode, and they get reviewed, tested, 
discussed and eventually fixed. It is much easier to report bugs 
in CureCode than it is to do so here. Please don't complain about 
the need to report bugs - that is what alpha means.

It doesn't matter that WINE is not a stable platform to test on - 
it's fixable, whereas Windows is not. We will try to make things 
work.

However, native support for R3 on Linux and other WINE platforms 
will continue to be a higher priority than WINE support.

Graham, if you want to form file paths without checking whether the 
directory portion has a trailing #"/" do this:
    blah: %dir
    f: blah/(file)
instead of
    f: join blah file

I use that trick with these a lot:
    .: %./
    ..: %../
then you can do this:
    read ../blah.r

GiuseppeC, I think that from a /core perspective that R3 is more 
mature than R2.

As far as design goes, I would agree, Paul. As far as stability goes, 
not yet :(

Hoping Carl gets on those issues fast.

BrianH, I get the impression that modules is somewhat unknown territory 
along with tasks. Do you think that's the case?

Yes, though not as much so as tasks. There were some proposed semantics 
for modules that would depend on changes to the semantics of objects, 
good changes but it is unknown when or if they will happen. I expect 
that modules will be simple at first.

An include function is really unlikely because of binding issues, 
unless that function only returns a module reference and doesn't 
rebind the calling context with its exports. Binding order matters 
in REBOL.

Kaj, I've reported the EXISTS? bug you mentioned above (#604). Please 
report any additional bugs you find.

There is now a WINE platform choosable in CureCode.

Kaj, check out CureCode ticket #602 for your DIR? bug. If you can 
test the example code on WINE it would be appreciated.

Henrik, I changed the ticket to be more precise - my job as reviewer 
:)

It would probably be good to have FILEIZE, EXISTS-FILE? and EXISTS-DIR? 
functions in R3, with compatible backports to R2.

what would fileize do that to-file does not?

Done. Here is the R3 and R2 FILEIZE:

fileize: func [
	{Returns a copy of the path turned into a non-directory.}
	path [file! string! url!]
][
	path: copy path
	if #"/" = last path [clear back tail path]
	path
]

Here is the R3 DIR-EXISTS? and FILE-EXISTS?:

dir-exists?: func [
	"Returns TRUE if a file or URL exists and is a directory."
	target [file! url!]
][
	if #"/" <> last target [target: append copy target #"/"]
	'dir = select attempt [query target] 'type
]

file-exists?: func [
	"Returns TRUE if a file or URL exists and is not a directory."
	target [file! url!]
][
	if #"/" = last target [target: head clear back tail copy target]
	'file = select attempt [query target] 'type
]

Here is the R2 DIR-EXISTS? and FILE-EXISTS?:

dir-exists?: func [
	"Returns TRUE if a file or URL exists and is a directory."
	target [file! url!]
][
	if #"/" <> last target [target: append copy target #"/"]
	found? all [
		target: attempt [info? target]
		'directory = get in target 'type
	]
]

file-exists?: func [
	"Returns TRUE if a file or URL exists and is not a directory."
	target [file! url!]
][
	if #"/" = last target [target: head clear back tail copy target]
	found? all [
		target: attempt [info? target]
		'file = get in target 'type
	]
]

Graham, FILEIZE would get rid of any trailing / in the copy, as DIRIZE 
adds any missing /.

The above have been submitted. Time will tell if they are accepted, 
or will be included by default. They work though.

Brian, what is the replacement for get-modes in R3?  I'm want to 
see if I can now set creation and modification dates on directories 
yet.  (see if it is now fixed in R3).  I had to scrap a project before 
because of this.

GET-MODES and SET-MODES aren't in R3 yet.