in reply to Re: Implementing (elisp-like) buffers in Perl 6: how to do buffer-localisation of arbitrary package variables?
in thread Implementing (elisp-like) buffers in Perl 6: how to do buffer-localisation of arbitrary package variables?

You're still not making enough sense to make this workable. (And, like it or not, I'm the person who has to understand it--if I don't, you don't get it)

Emacs has the concept of a buffer and everything centers around it. That's fine. What perl construct are you proposing take its place? A class? A closure? A method? A file? Should it be tied to data and happen when that data is manipulated? If so, then what do you do when two pieces of data both override the same stuff?

Perl is not a text editor, and text editor metaphors don't always translate over. This would be one of those cases.

  • Comment on Re: Re: Implementing (elisp-like) buffers in Perl 6: how to do buffer-localisation of arbitrary package variables?

Replies are listed 'Best First'.
Re: Implementing (elisp-like) buffers in Perl 6: how to do buffer-localisation of arbitrary package variables?
by jonadab (Parson) on Apr 04, 2003 at 15:58 UTC
    You're still not making enough sense to make this workable. (And, like it or not, I'm the person who has to understand it--if I don't, you don't get it)

    You are not required to understand it. Another monk pointed out how it can be implemented without any changes to the Perl6 core. I can do it as a module. (Which is all I was wanting in the first place.)

    Emacs has the concept of a buffer and everything centers around it. That's fine. What perl construct are you proposing take its place? A class? A closure? A method? A file?

    A buffer, of course. Each buffer would be an instance of the buffer class from the module I want to create. I thought I was entirely clear from the outset that my primary intention was to implement buffers (as a module). buffer-local scoping is just one part of that.

    My original message said:

    So I was thinking, hey, with this nice flexible object model, could we implement buffers in Perl6 as a module and throw it on CPAN? So I started thinking about how that would work... A buffer, obviously, would be an object...

    How is that not clear?

    (I probably won't call the class "buffer", though, as that might lead to confusion. "textbuffer" perhaps, or "hunkoftext", or something. I don't need to decide the name right now.)


    for(unpack("C*",'GGGG?GGGG?O__\?WccW?{GCw?Wcc{?Wcc~?Wcc{?~cc' .'W?')){$j=$_-63;++$a;for$p(0..7){$h[$p][$a]=$j%2;$j/=2}}for$ p(0..7){for$a(1..45){$_=($h[$p-1][$a])?'#':' ';print}print$/}