From: Nikolai Weibull Date: 2003-10-10T02:38:45+09:00 Subject: Re: Extension Language for a Text Editor * gabriele renzi [Oct, 09 2003 09:10]: > the learning curve for casual user would be really less hard, and it > won't collide with already existing lisp based editors ;) True, but this isn't going to be an editor for the casual user either ;-) > Well, given that tab expansion, string replacing/finding, > byte/word/line count, justification and other stuff can be easily done > with one line of ruby... But remember that we're not going to operate on a File, or a String as such. > Anyway, I think the apis you make available from the core of the > editor would be something really important in this analisys. Yeah, but one could assume that they'd be the same for both languages. > >* Is Ruby good enough for the task at the moment, performance wise? > Sure :) Heh, short and to the point ;-). > >Also, is there any way of redefining the // operator for constructing > >regular expression objects? I'm planning on implementing a new regex > >syntax for the editor (to make searches/substitutions easier to > >describe). > well, you have the soruce code, dig in it and change what you need, if > you really need it :) If I go with Ruby I don't want to alter the core of the language. > Anyway, why would you do such a thing ? the regex language is quite > standardized now, why would you change it? Because the standardized regex language we have now sucks, like German, or French. (Only kidding, only kidding. I love French. German sucks though. (Am I still kidding?) ;-) Seriously, see the earlier reply I wrote. I want simple, easy, yet expressive. I don't want (?:...) and "\\\\". nikolai -- ::: name: Nikolai Weibull :: aliases: pcp / lone-star / aka ::: ::: born: Chicago, IL USA :: loc atm: Gothenburg, Sweden ::: ::: page: www.pcppopper.org :: fun atm: gf,lps,ruby,lisp,war3 ::: main(){printf(&linux["\021%six\012\0"],(linux)["have"]+"fun"-97);}