问题描述
您好，
甚至更专业的工具，Jboss等。
我见过越来越多的语言集成AOP，AspectJ（Java），
AspectR（Ruby）等。面向导向似乎确实可以从
a开发人员的角度出发。我想知道的是，如果有人在商品上b / b
规模是否正在使用AOSD开发商业产品？
开源开发有望获得业界的信任吗？它可以用于个人项目和其他开源材料，但是你的银行会接受它吗？这是AOP是新的这个事实，对于
最多，令人困惑的是，或者AOP是在
环境中开发的，它有开源。可能会阻止商业开发商接受AOP。
可能导致AOSD采用的主要特征是什么？ AOP是下一步来自OOP的
？是否有一些机会使用一些较小的b
语言来升级到Java和C ++？您对
科目的看法将不胜感激？设计功能是一回事，但
广泛采用是另一回事，或者是它？
你想要在这个主题上添加的任何东西都会受到赞赏/>
简短问卷。
感谢您的参与。
Shane Hassan。
Hello,
Aspect oriented Software development seems to be expanding in the
popular vision of developers, with more and more IDE ''add-ons'' and
even more specialized tools,Jboss etc.
I''ve seen more and more languages integrate AOP,AspectJ (Java),
AspectR(Ruby)etc.Aspect oriented does seem to be the place to go from
a developer standpoint.What I want to know is,if anybody on a
commercial scale is using AOSD to develop commercial products? Is an
Open Source development ever going to gain the trust of industry? It
may be ok for personal projects and other Open Source material but
will your bank ever accept it? Is it the fact that AOP is new and, for
most,confusing or is it the fact that AOP has developed in the
environment it has.i.e Open Source,that may dissuade commercial
development shops from accepting AOP.
What are the main features that may lead to AOSD adoption? Is AOP the
next step on from OOP? Is it another chance for some of the lesser
utilised languages to step up to Java and C++? Your opinions on the
subject would be appreciated? Design features are one thing but
widespread adoption is another, or is it?
Anything you care to add on the subject would be appreciated on this
short questionnaire.
http://www.geocities.com/aspect505
Thank you for your participation.
Shane Hassan.
http://www.geocities.com/aspect505
推荐答案
我不确定这是否可行。我只看过
概念的证明，但没有真正的用途。但只有在后一种情况下你才能看到
的问题。
我不喜欢它，因为它破坏了封装和分割代码
几个文件的
。也许这可以通过新的编辑来解决
但是更容易导致很大的混乱。
我最重要的用例到目前为止看到的是：
- 登录设施
- 调试代码
- 前/后条件
- 线程同步
1 + 2 + 3可以嵌入一种语言。这已经在埃菲尔完成了。
我不知道我是否真的想看到像
线程同步这样困难的事情。作为一个方面。
I''m not sure if this is a the way to go. I''ve only seen proof of
concept but no real use. But only in the latter case you can see the
problems.
I don''t like it because it breaks encapsulation and splitters the code
over a few files. Maybe that can be solved with new kind of editors
but it is much more easy to result in a big confusion.
The most important use cases that i''ve seen so far are:
- Logging facilities
- Debugging code
- Pre/Postconditions
- Threading synchronization
1+2+3 can be embedded in a language. This is already done in Eiffel.
I don''t know if i really want to see something as difficult as
"threading synchronization" as an aspect.
我不确定这是否可行。我只看过
概念的证明，但没有真正的用途。但只有在后一种情况下你才能看到
的问题。
我不喜欢它，因为它破坏了封装和分割代码
几个文件的
。也许这可以通过新的编辑来解决
但是更容易导致很大的混乱。
我最重要的用例到目前为止看到的是：
- 登录设施
- 调试代码
- 前/后条件
- 线程同步
1 + 2 + 3可以嵌入一种语言。这已经在埃菲尔完成了。
我不知道我是否真的想看到像
线程同步这样困难的事情。作为一个方面。
I''m not sure if this is a the way to go. I''ve only seen proof of
concept but no real use. But only in the latter case you can see the
problems.
I don''t like it because it breaks encapsulation and splitters the code
over a few files. Maybe that can be solved with new kind of editors
but it is much more easy to result in a big confusion.
The most important use cases that i''ve seen so far are:
- Logging facilities
- Debugging code
- Pre/Postconditions
- Threading synchronization
1+2+3 can be embedded in a language. This is already done in Eiffel.
I don''t know if i really want to see something as difficult as
"threading synchronization" as an aspect.
这篇关于面向方面的一切？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！