World: r3wp

Should be easy using a simple custom dialect.

and as part of the language?

built in ... I mean

Makes more sense to draft this in a simple function first, imho.

Ok, ... can try it out

Not likely in direct syntax for two reasons:
- P* is a valid word itself.

- Word lookup is done by pointer comparison, not string comparison.

so I could use a function that traverses the object doing string 
comparisons and returns the full path for me so I don't have to keep 
typing it

walk-path 'Obj/P*/D*/C*/Value

Exactly.

Test results:
A107: Total: 3822 Succeeded: 3769 Failed: 53
A108: Total: 3829 Succeeded: 3750 Failed: 79

These your tests? And did you redownload the build?

The publicly available testsuite. Yes.

Ah, we should check the tests to see if they are affected by the 
changes in semantics in A108.

I am looking thru the regressions now.

Also, see if there are any new tests succeeding.

https://gist.github.com/9457aa5b41bfd0b7edcb

If anyone wants to join.

Are the red lines failed tests?

Also, # means none now.

The green lines are new failures.

The red lines are tests which no longer fail.

Yes, that's a case where the testsuite needs updating.

Nice.

The first few new regressions indicate that the "make error!" semantics 
have changed.

DISARM has finally been removed. It has never been necessary in R3.

Yes. Would maybe make sense to keep it around for a while to warn 
that it is now gone.

We did that for more than a year. Now it is gone.

It only had a deprecation notice, no hard error (like e.g. LOAD/next 
has now).

I personally don't care either way.

The deprecation notice was in CureCode, when someone complained that 
it didn't work. From early 2009.

Yeah, and in the docstring.

Just looked back and we made that change in 2008. Wow.

It predated CureCode :)

The `make image!` errors in lines 42-43 seem to be real regressions.

Seems complement no longer works on images and silently fails.

The test on line 51 is a bug. See bug#1471, fixed in a108.

Yep.

58 is the result of # now being none.

And 75, 101, 102.

Same for 75.

112-122 are the result of fixing bug#1602.

128-131 is # again.

AS are 135-137 and 138-141.

And 150-152, 153-156.

Ok, and that's it.

170+ is a erronous paste of mine :)

Well, so that looks like one real regression (complement on image!).

I think that the error codes are checked now. Fix all your tests 
that try to make errors with codes not in system/catalog/errors.

176-180 are examples of this.

Refresh the page.