WSCOMP error

Comments:

Author Thread:

j.merrill

WSCOMP error
Posted: Monday, March 07, 2005 7:08 PM (EST)

Have you looked at the function EZWC? If your version of WSCOMP doesn't have it, just holler.

I have what I presume is a modified version of it (that I haven't offered to APL2000 in a while) -- each argument to EZWC is a workspace name or the tienumber of an existing wstofile file. If you put * before the name of the workspace, the file isn't erased at the end. So you can do

      '*basews' EZWC 'firstcopy'

and then do (after the display is finished)

      90 EZWC 'secondcopy'

(assuming that "basews" got tied to 90).

It probably needs some cleanup for the existence of the #XF... routines.

I also have a couple of little fns that set the "state" var appropriately. Fn SAME ses up a compare that's appropriate for wss that should be the same (no display of matching objects); SUBSET is for the case where the right-side ws is expected to be a subset of the left-side ws (so it doesn't list the things in left-side ws that aren't in right-side, but does show the right-side things not in left-side).

Any of these are available if you ask (and can wait a little while ). Unfortunately, the extremely enhanced tool for doing the fn compares that's in my copy is not known to be freely available -- but I could check to see if its creators mind much if I let it out here.



Nicolai.Ohm

WSCOMP error
Posted: Tuesday, March 08, 2005 9:09 AM (EST)

Thanks for the tip on EZWC
Tested it, but currently it does not work due to the new []INBUF bug in APL+Win 5.2:
The workspaces are just not loaded (see posting in this forum: Delayed Execution of )CLEAR via []INBUF

The additional features and functions you describe look promising, but I just would be happy to have one working solution to compare workspaces.

WSCOMP crashes in the above example because the RAINPRO function CH’GetMetrics
contains not standard APL code (not to say: faulty code). It just takes so long to figure out, what function contains the faulty code, and I think you should be able to compare workspaces with code bugs.



Rex.Swain

WSCOMP error
Posted: Tuesday, March 08, 2005 9:10 AM (EST)

I have been working on a modern workspace comparison tool. It's a ]usercommand that takes two workspace (or usercommand file) names and does the comparison directly (no wstofile files, no []inbuf).

You are presented with a gui form (Listview) showing functions and variables that are same/different/only in one ws/etc. You can double-click on a function to look at it with the editor.

To do a detailed comparison of two functions, I rely on the Araxis Merge product, which is the best $129 you'll ever spend on software. (A free trial is available.)

If you'd like to be a beta tester of this tool, please contact me by email at rex@rexswain.com.



Support

WSCOMP error
Posted: Tuesday, March 08, 2005 12:08 PM (EST)

The failure in WSCOMP is caused by the presence of the "//" on line 24 (see below) of CH‘GetMetrics:

      AM["metric"] = 0;   // C# equivalent required

The solution is to replace // with © (lamp).

APL2000 Support



Nicolai.Ohm

WSCOMP error
Posted: Wednesday, March 09, 2005 8:37 AM (EST)

That’s really NOT a solution because I’m not able to debug a workspace before comparing it due to time constraints


Nicolai.Ohm

WSCOMP error
Posted: Wednesday, March 09, 2005 8:52 AM (EST)

Here is how I worked it out. I added the hash # to the symbols variable in line[15] of function VRL

#‘symbols„'#„òºª¨›œµòòòòÐ¾†‡…¤“”!()*+,-./:;<=>?[\]^~¬—˜×Ž®þ™Þòòò¸¼ðò‹ƒ‚²´Šš’³¹‰ˆ•–÷°±Ÿ½ž|'
© BENCHUM: added #

so long everything works fine.