Bug 72379 - static aspects not well explained
Summary: static aspects not well explained
Status: RESOLVED FIXED
Alias: None
Product: AspectJ
Classification: Tools
Component: Docs (show other bugs)
Version: 1.2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 1.2.1   Edit
Assignee: Erik Hilsdale CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 19:12 EDT by Erik Hilsdale CLA
Modified: 2004-10-21 04:31 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Hilsdale CLA 2004-08-20 19:12:43 EDT 
From an email from Jonathan Amir:

2) In section 1, heading "Development Aspects", sub heading "Contract
Enforement", there is an example that declares a static aspect. To the best of
my knowledge, the keyword "static", when used before an aspect declaration,
declares the aspect to be a subclass of another class (similarly to the static
class declarations in Java). However, the problem that I want to point out is
that this is not mentioned anyway in the documentations (or at least I couldn't
find it), and this issue puzzled me for a while.
Comment 1 Erik Hilsdale CLA 2004-08-22 21:56:51 EDT 
Yowza!  It turns out this was a holdover from AspectJ 0.8 when we had the notion
of a top-level static aspect.  Needless to say, this is gone now.  I simply 
deleted the static modifier from the code in gettingstarted and shook my head
in shame for not doing so two years ago.

As a bonus, I've lightly clarified the semantics guide with respect to 
static aspects.
Comment 2 Adrian Colyer CLA 2004-10-21 04:31:05 EDT 
Fix released as part of AspectJ 1.2.1