Joose.Manual.FAQ - Frequently asked questions about Joose
Yes! Many sites with household names are using Joose to build high-traffic services. Countless others are using Joose in production.
Yes. The sugary API, the one 95% of users will interact with, is very stable. Any changes will be 100% backwards compatible.
The meta API is less set in stone. We reserve the right to tweak parts of it to improve efficiency or consistency. This will not be done lightly. We do perform deprecation cycles. We really do not like making ourselves look bad by breaking your code. Submitting test cases is the best way to ensure that your code is not inadvertently broken by refactoring.
Ideally, you should never write your own constructor, and should use Joose's other features to handle your specific object construction needs.
beforeto stop execution of a method?
before modifier execute original method unconditionally. Use
around modifiers instead.
In Joose, a trait is almost exactly the same thing as a role, which is usually composed into an instance of a class at runtime to add or modify the behavior of just that instance.
Outside the context of Joose, traits and roles generally mean exactly the same thing. The original paper called them Traits, however Perl 6 will call them Roles.
Yes, you can use aliases Joose.Class, Joose.Role and Joose.Module to declare your classes.
Nickolay Platonov firstname.lastname@example.org
Heavily based on the original content of Moose::Manual, by Dave Rolsky email@example.com
Copyright (c) 2008-2011, Malte Ubl, Nickolay Platonov
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.