On Wed, Sep 3, 2014 at 7:35 AM, Father Chrysostomos <sprout@cpan.org> wrote: > sawyer x wrote: > > I know this is considered a naughty word in some places > > It's not really naughty; it just implies organization, which is wish- > ful thinking. :-) > :) > > * Are there any long-term changes desired? I know CoW went in some time > > ago. Anything like that? > > What do you mean by 'like that'? :-) > You can label it as "big stuff" or "cool things". :) Though, in all seriousness, I think CoW is a major step forward. Basically, todo.pod and the RT system (the latter more than the for- > mer) are my to-do list. Plus any bugs I run into. > Are these leading to anything specific? (and I do apologize if that sounded or was disrespectful in any way) And, when I have an itch, I work on bigger things. My current list of > bigger things is something like this: > > - Reduce memory usage by avoiding the need for GVs to hold most subs > > - Lvalue references > > - Get Deparse working flawlessly > > - Fix line number bugs once and for all > > - Get formats to respect Unicode character widths > > - Finish making all keywords into CORE:: subs > > - Error codes, not just text strings that are reworded every so often > > - Various attributes for subs to affect parsing: > :list (list assignment), :iter (implicit $_= in while) > > - (\.) prototype that accepts any scalar expression and references it > > Most of those are either very hard or controversial, so this stuff > happens slowly. > If any of these were formalized into "part of the plan" or "required necessities to complete the plan", it would be less controversial, and perhaps it would be easier to get help for doing it? What I can identify here that I would put under a plan is: * Reduce memory usage. * Improve debugging tools (Deparse). * Improve Unicode support. * Solidify keywords as CORE:: subs. * Improve parsing. But, since these are still general topics, they lead to a general direction. I would still want these to be part of a bigger effort.Thread Previous | Thread Next