Bazyli Brzóska

Yes, I totally agree @adudek. We'll take this into consideration when planning 3.0. Thanks for your feedback!

Hi @Cj-bc these are some good points I could improve on in the README. ### 1. "lossless dumping" in this context means the capturing of the descriptor of any given...

@nicutor's answer is correct. In the current version logging is a bit over-engineered. I'd like to simplify it in the next version that we're brainstorming in #45, feel free to...

@DwordPtr I have not tested. I would assume some incompatibility, but it's definitely possible to port it.

@sdrausty we're planning a re-write of the framework in 3.0 release, so we can take this into account :) See the issue here: #45

@constrict0r, that's some hefty work indeed. Pretty cool! @rbukovansky to answer your questions: 1. creating collections of class instances is a bit tricky for now, but you can capture the...

Fix is here, in the rewrite of the named parameters functionality: https://github.com/niieani/bash-oo-framework/issues/41#issuecomment-362107200. To get it merged I'd need to provide a backwards-compatible layer for the older syntax, I didn't have...

Great points @tterranigma! I wholeheartedly agree about the clean-slate and all of your criteria for it. Just as I've started with the re-write of named parameters -- a clean slate...

Indeed, this is a serious problem. I've thought about it for a while and come up with a re-written, simpler (but more powerful) way to declare and assign parameters. It...

Thanks for the feedback! I think old aliases could be ported - I was thinking how to do it and it shouldn't be too hard to add. As for the...