Ok, in this way I preserve the original code, but the problem is I need to implement a new dialect to to be used in batch (like in a program) but I need to use it in "live", from command console.
It means if I create a standard dialect it could become really annoing use it. E.g.: >> mydialect [ myCommand ] You can see I need to type many things. Since I'm creating something like a dos-shell, I need to creating fast typing commands. Look at another example: DOS SHELL: >> copy file1 file2 MY FUTURE SHELL: >> mydialect [ copy file1 file2 ] I typed too many things! Another way could be creating new commands with a prefix (but I don't like this solution): >>jcopy file1 file2 Any other ideas? On 5/10/06, Luca Truffarelli <[EMAIL PROTECTED]> wrote: > > You can "save" the existing ones before modify them. > > >> oldprint: :print > >> print: func [value][oldprint mold value] > >> oldprint "1" > 1 > >> print "1" > "1" > > > > Hi, > > > > I need a suggestion how to implement a new dialect, linked to the > > global context, but without iterfering with existing words (commands). > > > > I need to implement these commands in the global context since I need > > a user to do something like this (using a console I'm building): > > > > >> print mydirCommand > > > > Where "print" is the standard command, but "mydirCommand" is a custom > comma=3D > > nd. > > The problem is I think many commands I need to create will overlap > > standard commands. > > > > E.g.: "copy" command in Rebol already exists, but I want to create a > > new command to "copy" like the copy function for files (like copy > > command implemented in Ms-DOS/Win, or "cp" in Linux). > > > > >> copy %/c/temp %/c/temp2 > > > > Can you suggest me some solutions, workarounds, etc...? > > -- > To unsubscribe from the list, just send an email to > lists at rebol.com with unsubscribe as the subject. > > -- To unsubscribe from the list, just send an email to lists at rebol.com with unsubscribe as the subject.
