Last 7 days

• Nov 20, 2009

  issue 32 (Support non-Apple systems with GnuStep) commented on by eric....@am.sony.com   -   Alex and Ryan, I have objectivEClipe working on Linux. I just changed the library path and header path point to GNUstep. It can build and run objective c projects. But I need help with gdb debugger. It started gdb->gdb/mi but I could not do single step. GDB works in command line. The eclipse console shows: .gdbinit: No such file or directory Stopped due to shared library even [0] cancel [1] all [2] -[NSOperation main] at NSOperation.m:101 [3] -[MSThread main] at NSThread.m:736 [4] main at ../src/ImageViewe.m: 200 > The ImageViewer.m line 200 is my main. I tried different configurations, it still stopped at the same point.

  Alex and Ryan, I have objectivEClipe working on Linux. I just changed the library path and header path point to GNUstep. It can build and run objective c projects. But I need help with gdb debugger. It started gdb->gdb/mi but I could not do single step. GDB works in command line. The eclipse console shows: .gdbinit: No such file or directory Stopped due to shared library even [0] cancel [1] all [2] -[NSOperation main] at NSOperation.m:101 [3] -[MSThread main] at NSThread.m:736 [4] main at ../src/ImageViewe.m: 200 > The ImageViewer.m line 200 is my main. I tried different configurations, it still stopped at the same point.
• Nov 18, 2009

  issue 47 (Objectiveclipse does not appear to work with latest version ...) commented on by matthieu.cormier   -   I attempted installing CDT into a Java based 3.5.1 version of eclipse. http://www.eclipse.org/downloads/download.php? file=/technology/epp/downloads/release/galileo/SR1/eclipse-java-galileo-SR1-win32.zip Then installed CDT 6.0.0 and then attempted to install objectivEclipse but I received a different cryptic error: Cannot complete the install because one or more required items could not be found. Missing requirement: 1258568915013 0.0.0.1258568915013 requires 'org.eclipse.cdt.objc.feature.feature.group [0.2.0]' but it could not be found

  I attempted installing CDT into a Java based 3.5.1 version of eclipse. http://www.eclipse.org/downloads/download.php? file=/technology/epp/downloads/release/galileo/SR1/eclipse-java-galileo-SR1-win32.zip Then installed CDT 6.0.0 and then attempted to install objectivEclipse but I received a different cryptic error: Cannot complete the install because one or more required items could not be found. Missing requirement: 1258568915013 0.0.0.1258568915013 requires 'org.eclipse.cdt.objc.feature.feature.group [0.2.0]' but it could not be found
• Nov 18, 2009

  issue 47 (Objectiveclipse does not appear to work with latest version ...) commented on by matthieu.cormier   -   This appears to be a known issue. http://groups.google.com/group/objectiveclipse- dev/browse_thread/thread/1bd0a45f916882d2# I am currently attempting to use objectiveclipse with cdt-master-6.0.0.zip. http://www.eclipse.org/downloads/download.php? file=/tools/cdt/releases/galileo/dist/cdt-master-6.0.0.zip

  This appears to be a known issue. http://groups.google.com/group/objectiveclipse- dev/browse_thread/thread/1bd0a45f916882d2# I am currently attempting to use objectiveclipse with cdt-master-6.0.0.zip. http://www.eclipse.org/downloads/download.php? file=/tools/cdt/releases/galileo/dist/cdt-master-6.0.0.zip
• Nov 18, 2009

  issue 47 (Objectiveclipse does not appear to work with latest version ...) reported by matthieu.cormier   -   What steps will reproduce the problem? 1. Update to latest CDT with the install URL http://download.eclipse.org/tools/cdt/releases/galileo 2. Attempt to install objectiveclipse http://objectiveclipse.googlecode.com/svn/update/site.xml What is the expected output? What do you see instead? Cannot complete the install because one or more required items could not be found. Missing requirement: 1258557492491 0.0.0.1258557492491 requires 'org.eclipse.cdt.objc.feature.feature.group [0.2.0]' but it could not be found What version of the product are you using? On what operating system? Latest version of CDT eclipse on Windows.

  What steps will reproduce the problem? 1. Update to latest CDT with the install URL http://download.eclipse.org/tools/cdt/releases/galileo 2. Attempt to install objectiveclipse http://objectiveclipse.googlecode.com/svn/update/site.xml What is the expected output? What do you see instead? Cannot complete the install because one or more required items could not be found. Missing requirement: 1258557492491 0.0.0.1258557492491 requires 'org.eclipse.cdt.objc.feature.feature.group [0.2.0]' but it could not be found What version of the product are you using? On what operating system? Latest version of CDT eclipse on Windows.

Earlier this year

• Oct 20, 2009

  GettingStarted (How to checkout, build and compile the project) Wiki page commented on by ashokragu   -   When tried getting the following error Unhandled event loop exception java.lang.NullPointerException at org.eclipse.cdt.ui.wizards.CDTMainWizardPage.switchTo(CDTMainWizardPage.java:403) at org.eclipse.cdt.ui.wizards.CDTMainWizardPage.createControl(CDTMainWizardPage.java:93) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:675) at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1093) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1152) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149) at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138)

  When tried getting the following error Unhandled event loop exception java.lang.NullPointerException at org.eclipse.cdt.ui.wizards.CDTMainWizardPage.switchTo(CDTMainWizardPage.java:403) at org.eclipse.cdt.ui.wizards.CDTMainWizardPage.createControl(CDTMainWizardPage.java:93) at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:170) at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:675) at org.eclipse.jface.wizard.WizardDialog.setWizard(WizardDialog.java:1093) at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1152) at org.eclipse.jface.wizard.WizardDialog.access$2(WizardDialog.java:1149) at org.eclipse.jface.wizard.WizardDialog$5.run(WizardDialog.java:1138)
• Oct 12, 2009

  issue 32 (Support non-Apple systems with GnuStep) commented on by alex.blewitt   -   Hi Eric I really need to release a new build with the mac-specific restrictions so that it's more generally applicable. I've been caught up with other projects but want to devote more time to this soon.

  Hi Eric I really need to release a new build with the mac-specific restrictions so that it's more generally applicable. I've been caught up with other projects but want to devote more time to this soon.
• Oct 12, 2009

  issue 32 (Support non-Apple systems with GnuStep) commented on by eric.yam@am.sony.com   -   Alex and Ryan, is there a version of non-Apple objectivEClipe with GNUStep I could help to test?

  Alex and Ryan, is there a version of non-Apple objectivEClipe with GNUStep I could help to test?
• Oct 12, 2009

  GettingStarted (How to checkout, build and compile the project) Wiki page commented on by eric....@am.sony.com   -   Alex, I am trying to build the ObjectivEClipse using Linux. Could you help? I have CDT and PDE.

  Alex, I am trying to build the ObjectivEClipse using Linux. Could you help? I have CDT and PDE.
• Sep 28, 2009

  Mylyn (Using Mylyn with ObjectivEClipse) Wiki page commented on by alex.blewitt   -   I updated the 2nd image to say 'with a mylyn task active'. Thanks.

  I updated the 2nd image to say 'with a mylyn task active'. Thanks.
• Sep 28, 2009

  Mylyn (Using Mylyn with ObjectivEClipse) Wiki page edited by alex.blewitt   -   Revision r145 Changed without -> with in right place

  Revision r145 Changed without -> with in right place
• Sep 28, 2009

  issue 19 (Set up automated build) commented on by alex.blewitt   -   I've finally got around to building a virtual box to handle the checkout/build of this project, so this is finally getting some traction.

  I've finally got around to building a virtual box to handle the checkout/build of this project, so this is finally getting some traction.
• Sep 25, 2009

  Mylyn (Using Mylyn with ObjectivEClipse) Wiki page commented on by Changning.Zhou   -   I think you messed up the two pictures

  I think you messed up the two pictures
• Sep 24, 2009

  GettingStartedWithGit (How to use Git to checkout ObjectivEClipse) Wiki page edited by alex.blewitt   -   Revision r144 Minor typo

  Revision r144 Minor typo
• Sep 24, 2009

  GettingStartedWithGit (How to use Git to checkout ObjetivEClipse) Wiki page added by alex.blewitt   -   Revision r143 Added how to get a version of this repository from Git

  Revision r143 Added how to get a version of this repository from Git
• Sep 22, 2009

  issue 46 (Support weak linked libraries/frameworks) reported by alex.blewitt   -   A framework can be weakly linked to allow for other libraries to be added later on. The same is true of libraries, but may be more generally useful for frameworks which don't exist on a prior version of a platform.

  A framework can be weakly linked to allow for other libraries to be added later on. The same is true of libraries, but may be more generally useful for frameworks which don't exist on a prior version of a platform.
• Sep 17, 2009

  issue 45 (Support parsing block format) commented on by rrusaw   -   Initial implementation in r142

  Initial implementation in r142
• Sep 17, 2009

  r142 (Added initial support for parsing block object expressions w...) committed by rrusaw   -   Added initial support for parsing block object expressions with some simple unit tests.

  Added initial support for parsing block object expressions with some simple unit tests.
• Sep 17, 2009

  1 issue changed by rrusaw   -   Issue 45

  Issue 45
• Sep 08, 2009

  issue 45 (Support parsing block format) commented on by rrusaw   -   Should be doable to at least parse them. I'll have a look when I get some free time.

  Should be doable to at least parse them. I'll have a look when I get some free time.
• Sep 03, 2009

  issue 45 (Support parsing block format) reported by alex.blewitt   -   Blocks are new (for 10.6) as a way of allowing functions to be passed in. We should parse the syntax for blocks in ObjectivEClipse, even if we can't do much with it at the moment. http://developer.apple.com/mac/library/documentation/General/Conceptual/DevPedia- CocoaCore/Block.html Example from above: int (^oneFrom)(int); oneFrom = ^(int anInt) { return anInt - 1; };

  Blocks are new (for 10.6) as a way of allowing functions to be passed in. We should parse the syntax for blocks in ObjectivEClipse, even if we can't do much with it at the moment. http://developer.apple.com/mac/library/documentation/General/Conceptual/DevPedia- CocoaCore/Block.html Example from above: int (^oneFrom)(int); oneFrom = ^(int anInt) { return anInt - 1; };
• Aug 06, 2009

  issue 44 (Tab should move between @bits in headerdoc) reported by alex.blewitt   -   In a HeaderDoc comment, pressing Tab should move you to the next field, and optionally highlight the text present /*! * @foo Foo$ * @bar Bar */ cursor at $ before In a HeaderDoc comment, pressing Tab should move you to the next field, and optionally highlight the text present /*! * @foo Foo * @bar $[Bar] */ cursor at $ afterwards with [text] selected last value - cycle to top? Also support shift tab to go other way?

  In a HeaderDoc comment, pressing Tab should move you to the next field, and optionally highlight the text present /*! * @foo Foo$ * @bar Bar */ cursor at $ before In a HeaderDoc comment, pressing Tab should move you to the next field, and optionally highlight the text present /*! * @foo Foo * @bar $[Bar] */ cursor at $ afterwards with [text] selected last value - cycle to top? Also support shift tab to go other way?
• Aug 06, 2009

  r141 (Fix test so that we test the parameter and return generation...) committed by alex.blewitt   -   Fix test so that we test the parameter and return generation items

  Fix test so that we test the parameter and return generation items
• Aug 06, 2009

  r140 (Added more test cases for header doc generation) committed by alex.blewitt   -   Added more test cases for header doc generation

  Added more test cases for header doc generation
• Aug 05, 2009

  issue 40 (HeaderDoc support) commented on by alex.blewitt   -   For those tracking this bug, I've committed r139 which allows you to put /*! as the start of a HeaderDoc block, and above a function and a method, generate a HeaderDoc template. I've not yet completed the full list of HeaderDoc tags, nor does it work above classes (or file headers) at the moment. This will temporarily affect mouse-overs that will display a standard C header and source code, though I'm hoping to improve that subsequently. In order to see this, you'll need to change the document handler to be 'headerdoc' in the project, by right- clicking on the project and going to C/C++ General, enabling project specific settings, and selecting 'HeaderDoc' from the drop-down list. This will be the default on Mac platforms eventually going forward unless anyone objects.

  For those tracking this bug, I've committed r139 which allows you to put /*! as the start of a HeaderDoc block, and above a function and a method, generate a HeaderDoc template. I've not yet completed the full list of HeaderDoc tags, nor does it work above classes (or file headers) at the moment. This will temporarily affect mouse-overs that will display a standard C header and source code, though I'm hoping to improve that subsequently. In order to see this, you'll need to change the document handler to be 'headerdoc' in the project, by right- clicking on the project and going to C/C++ General, enabling project specific settings, and selecting 'HeaderDoc' from the drop-down list. This will be the default on Mac platforms eventually going forward unless anyone objects.
• Aug 05, 2009

  issue 43 (Enter in HeaderDoc comment often moves to wrong place) Status changed by alex.blewitt   -   Fixed in r139

  Status: Verified

  Fixed in r139

  Status: Verified
• Aug 05, 2009

  r139 (Fix bug 43 introduced by r137 and add test case (further tes...) committed by alex.blewitt   -   Fix bug 43 introduced by r137 and add test case (further test cases still needed)

  Fix bug 43 introduced by r137 and add test case (further test cases still needed)
• Aug 05, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by alex.blewitt   -   Sounds good. Can you file a separate issue so we can distinguish this one (clang) from cppcheck?

  Sounds good. Can you file a separate issue so we can distinguish this one (clang) from cppcheck?
• Aug 04, 2009

  issue 43 (Enter in HeaderDoc comment often moves to wrong place) reported by alex.blewitt   -   I've introduced a bug with r138 when enter is pressed in a HeaderDoc comment. Going to need to figure that out for a while. Non-header doc comments (those beginning /* or /**) are not affected. /*!(return) will generate HeaderDoc comments in right place; subsequent comments are misplaced. Simialrly, if the indent is non-zero, then the comments are wrong.

  I've introduced a bug with r138 when enter is pressed in a HeaderDoc comment. Going to need to figure that out for a while. Non-header doc comments (those beginning /* or /**) are not affected. /*!(return) will generate HeaderDoc comments in right place; subsequent comments are misplaced. Simialrly, if the indent is non-zero, then the comments are wrong.
• Aug 04, 2009

  r138 (Add HeaderDoc support for documentation types) committed by alex.blewitt   -   Add HeaderDoc support for documentation types

  Add HeaderDoc support for documentation types
• Aug 04, 2009

  r137 (Removed IASTHeaderDoc and friends) committed by alex.blewitt   -   Removed IASTHeaderDoc and friends

  Removed IASTHeaderDoc and friends
• Aug 04, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by konra...@gmx.de   -   I just successfully tried to embed cppcheck with the Codan framework (only using its error logging capabilities and option to run the check with the build). The part, which is already in CVS is at least a good starting point and makes it very easy to embed external code checkers. You could make use of that code already in svn to release the ObjectiveEClipse static analysis. Then it would be easier to port it to that framework if it becomes part of a future Eclipse CDT release. But this is of course only a suggestion. If you are interested I can give you the source (very rough draft) I wrote to embed cppcheck.

  I just successfully tried to embed cppcheck with the Codan framework (only using its error logging capabilities and option to run the check with the build). The part, which is already in CVS is at least a good starting point and makes it very easy to embed external code checkers. You could make use of that code already in svn to release the ObjectiveEClipse static analysis. Then it would be easier to port it to that framework if it becomes part of a future Eclipse CDT release. But this is of course only a suggestion. If you are interested I can give you the source (very rough draft) I wrote to embed cppcheck.
• Aug 04, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by alex.blewitt   -   The static analysis framework isn't part of the Galileo release, which is what ObjectivEClipse is currently targetting, whereas the clang static tool is something that can be applied to an existing system.

  The static analysis framework isn't part of the Galileo release, which is what ObjectivEClipse is currently targetting, whereas the clang static tool is something that can be applied to an existing system.
• Aug 03, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by konra...@gmx.de   -   This would be a great feature, but you should consider using the new CDT framework for static analysis (http://wiki.eclipse.org/CDT/designs/StaticAnalysis) for this job. I don't know how much is really implemented but it should be worth trying out.

  This would be a great feature, but you should consider using the new CDT framework for static analysis (http://wiki.eclipse.org/CDT/designs/StaticAnalysis) for this job. I don't know how much is really implemented but it should be worth trying out.
• Aug 02, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by rrusaw   -   The clang analyzer isn't LGPL, its distributed under the LLVM license, which appears to be a '3 clause BSD' style license. Regardless I hadn't intended that we'd include the analyzer, just provide an interface to one that the user already has installed.

  The clang analyzer isn't LGPL, its distributed under the LLVM license, which appears to be a '3 clause BSD' style license. Regardless I hadn't intended that we'd include the analyzer, just provide an interface to one that the user already has installed.
• Aug 02, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by alex.blewitt   -   FWIW I tried to run scan-build on a CDT project from the terminal, and it didn't seem to generate any reports. I'm not sure if I have some odd directory set up, but it would be worth confirming that we can run scan-build externally to the CDT project before trying to hook it in.

  FWIW I tried to run scan-build on a CDT project from the terminal, and it didn't seem to generate any reports. I'm not sure if I have some odd directory set up, but it would be worth confirming that we can run scan-build externally to the CDT project before trying to hook it in.
• Aug 02, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by alex.blewitt   -   NB I think an additional tool is probably a good idea rather than a builder - as the documentation notes, it's quite time consuming (and requires a full build). So having this build every time might be overly expensive. On the other hand, having it as a tool which can be run in the background might be useful.

  NB I think an additional tool is probably a good idea rather than a builder - as the documentation notes, it's quite time consuming (and requires a full build). So having this build every time might be overly expensive. On the other hand, having it as a tool which can be run in the background might be useful.
• Aug 02, 2009

  issue 42 (Add problem marker support for clang static analyzer.) commented on by alex.blewitt   -   Sounds like a good goal. However, the clang analyser is LGPL and LLVM so we'd need to be careful about redistribution. It would probably be enough to have the ObjectivEClipse code be able to parse the output from clang, and translate those (but without shipping the clang itself). It might be the case that we could package up a version of clang for invocation programmatically in a bundle but would have to be done outside of the core objectiveclipse bundles (though I don't see any reason why we couldn't host it on this project in a separate bundle). If there's any question of licensing issues for later inclusion at Eclipse.org, we'd simply leave the binary bundle behind. I note that the build instructions say 'this can take some time'. It also seems to need to ahve a full build done; if you run it, then run it a second time, it will say 'nothing to do' (at least, via xcodebuild). If you run it without -v, the output doesn't get generated but simply dumped into HTML files (which won't be easy to parse). On the other hand, if you run it with -v, it gives you the message and file/location name, which should be easy enough to hook in. alex$ scan-build -v -o foo xcodebuild -sdk iphonesimulator3.0 | grep "Value stored" 2009-08-02 08:40:25.562 xcodebuild[33448:613] warning: compiler 'com.apple.compilers.llvm.clang.1_0.analyzer' is based on missing compiler 'com.apple.compilers.llvm.clang.1_0.analyzer' /Users/alex/Projects/MyProject/Foo.m:660:25: warning: Value stored to 'foobar' is never read I suspect that if you just replaced the 'gcc' phase with 'scan-build' in the project's makefile, and did a clean all, then it would just display the values as expected.

  Sounds like a good goal. However, the clang analyser is LGPL and LLVM so we'd need to be careful about redistribution. It would probably be enough to have the ObjectivEClipse code be able to parse the output from clang, and translate those (but without shipping the clang itself). It might be the case that we could package up a version of clang for invocation programmatically in a bundle but would have to be done outside of the core objectiveclipse bundles (though I don't see any reason why we couldn't host it on this project in a separate bundle). If there's any question of licensing issues for later inclusion at Eclipse.org, we'd simply leave the binary bundle behind. I note that the build instructions say 'this can take some time'. It also seems to need to ahve a full build done; if you run it, then run it a second time, it will say 'nothing to do' (at least, via xcodebuild). If you run it without -v, the output doesn't get generated but simply dumped into HTML files (which won't be easy to parse). On the other hand, if you run it with -v, it gives you the message and file/location name, which should be easy enough to hook in. alex$ scan-build -v -o foo xcodebuild -sdk iphonesimulator3.0 | grep "Value stored" 2009-08-02 08:40:25.562 xcodebuild[33448:613] warning: compiler 'com.apple.compilers.llvm.clang.1_0.analyzer' is based on missing compiler 'com.apple.compilers.llvm.clang.1_0.analyzer' /Users/alex/Projects/MyProject/Foo.m:660:25: warning: Value stored to 'foobar' is never read I suspect that if you just replaced the 'gcc' phase with 'scan-build' in the project's makefile, and did a clean all, then it would just display the values as expected.
• Aug 01, 2009

  issue 42 (Add problem marker support for clang static analyzer.) Owner changed by rrusaw   -  

  Owner: ---

  Owner: ---
• Aug 01, 2009

  issue 42 (Add problem marker support for clang static analyzer.) reported by rrusaw   -   It should be possible to generate IProblem markers from the output of the clang static analysis tool, http://clang-analyzer.llvm.org/, either through a configured project builder or action.

  It should be possible to generate IProblem markers from the output of the clang static analysis tool, http://clang-analyzer.llvm.org/, either through a configured project builder or action.
• Jul 31, 2009

  issue 40 (HeaderDoc support) commented on by alex.blewitt   -   We could do extra parsing of the comment header whilst we do the parsing - in the meantime, we can get it out of the translation unit as a string for the comment. Hovers are contributed via the UI plugin as follows: <extension point="org.eclipse.cdt.ui.textHovers"> <hover label="%cdocHover" description="%cdocHoverDescription" class="org.eclipse.cdt.internal.ui.text.c.hover.CDocHover" id="org.eclipse.cdt.ui.CDocHover"> </hover> <hover label="%sourceHover" description="%sourceHoverDescription" class="org.eclipse.cdt.internal.ui.text.c.hover.CSourceHover" id="org.eclipse.cdt.ui.CSourceHover"> </hover> </extension> The one that's currently used is CSourceHover, which is what gets instantiated at the moment. The CDocHeader doesn't appear to give anything at present, but it may be possible that we can hook into delivering the documentation into the help system. The CHelpProviderManager maintains a cache of data, and it's possible we can just feed the items into there. There is a HelpInfo which can contributed Help documents

  We could do extra parsing of the comment header whilst we do the parsing - in the meantime, we can get it out of the translation unit as a string for the comment. Hovers are contributed via the UI plugin as follows: <extension point="org.eclipse.cdt.ui.textHovers"> <hover label="%cdocHover" description="%cdocHoverDescription" class="org.eclipse.cdt.internal.ui.text.c.hover.CDocHover" id="org.eclipse.cdt.ui.CDocHover"> </hover> <hover label="%sourceHover" description="%sourceHoverDescription" class="org.eclipse.cdt.internal.ui.text.c.hover.CSourceHover" id="org.eclipse.cdt.ui.CSourceHover"> </hover> </extension> The one that's currently used is CSourceHover, which is what gets instantiated at the moment. The CDocHeader doesn't appear to give anything at present, but it may be possible that we can hook into delivering the documentation into the help system. The CHelpProviderManager maintains a cache of data, and it's possible we can just feed the items into there. There is a HelpInfo which can contributed Help documents
• Jul 31, 2009

  r136 (Added support for parsing HeaderDoc tags from the files) committed by alex.blewitt   -   Added support for parsing HeaderDoc tags from the files

  Added support for parsing HeaderDoc tags from the files
• Jul 31, 2009

  r135 (Added @SuppressWarnings to remove the restricted item warnin...) committed by alex.blewitt   -   Added @SuppressWarnings to remove the restricted item warnings that were getting in the way

  Added @SuppressWarnings to remove the restricted item warnings that were getting in the way
• Jul 31, 2009

  r134 (Removed redundant interface implementation) committed by alex.blewitt   -   Removed redundant interface implementation

  Removed redundant interface implementation
• Jul 30, 2009

  issue 40 (HeaderDoc support) commented on by alex.blewitt   -   HeaderDoc is documented at Apple: http://developer.apple.com/darwin/projects/headerdoc/ A HeaderDoc comment is an ordinary C comment with a leading bang: /*! This is headerdoc */ It can also have leading * like Java (and it might be preferable for ObjectivEClipse to put in the leading * for consistency's sake) /*! * This is also headerdoc */ Unlike JavaDoc, where the first sentence is used as a one-liner and the remainder is used as text, HeaderDoc uses @abstract for the one-liner and @description for the full text. You can also use other @ keywords, like @class, @function, @method, @interface, @protocol to document those types of items. Here's an incomplete list of the headers we should probably support/parse: * @class ClassName * @method foo:withBar:andBar: * @protocol ProtocolName * @abstract OneLiner for Table of Contents * @discussion More detailed discussion, possibly multiple lines or following text * @throws ExceptionName * @param bar The Bar parameter * @return or @result The Return Value * @version Version Number (e.g. $Id$ ) * @Updated yyyy-mm-dd When it was last touched There are others, which we might want to have as keywords for auto-completion, but probably leave to a subsequent iteration to complete: * @struct StructName * @typedef TypeDefName * @union UnionName * @var GlobalVarName * @enum EnumName * @file FileName * @framework FrameworkName * @functiongroup Function Group name (like #pragma mark blocks?) * @const ConstantName * @define or @defined HashDef Name * @field FIeldName (structs etc.) * @deprecated Deprecated In Version Foo There's also esoteric support for inclusion in different versions of a product: * @availabilitymacro DEFINED Shows up as Available In: String if DEFINED is defined

  HeaderDoc is documented at Apple: http://developer.apple.com/darwin/projects/headerdoc/ A HeaderDoc comment is an ordinary C comment with a leading bang: /*! This is headerdoc */ It can also have leading * like Java (and it might be preferable for ObjectivEClipse to put in the leading * for consistency's sake) /*! * This is also headerdoc */ Unlike JavaDoc, where the first sentence is used as a one-liner and the remainder is used as text, HeaderDoc uses @abstract for the one-liner and @description for the full text. You can also use other @ keywords, like @class, @function, @method, @interface, @protocol to document those types of items. Here's an incomplete list of the headers we should probably support/parse: * @class ClassName * @method foo:withBar:andBar: * @protocol ProtocolName * @abstract OneLiner for Table of Contents * @discussion More detailed discussion, possibly multiple lines or following text * @throws ExceptionName * @param bar The Bar parameter * @return or @result The Return Value * @version Version Number (e.g. $Id$ ) * @Updated yyyy-mm-dd When it was last touched There are others, which we might want to have as keywords for auto-completion, but probably leave to a subsequent iteration to complete: * @struct StructName * @typedef TypeDefName * @union UnionName * @var GlobalVarName * @enum EnumName * @file FileName * @framework FrameworkName * @functiongroup Function Group name (like #pragma mark blocks?) * @const ConstantName * @define or @defined HashDef Name * @field FIeldName (structs etc.) * @deprecated Deprecated In Version Foo There's also esoteric support for inclusion in different versions of a product: * @availabilitymacro DEFINED Shows up as Available In: String if DEFINED is defined
• Jul 27, 2009

  r133 (Delete empty package) committed by alex.blewitt   -   Delete empty package

  Delete empty package
• Jul 27, 2009

  r132 (Added ObjC specific common navigator provider) committed by alex.blewitt   -   Added ObjC specific common navigator provider

  Added ObjC specific common navigator provider
• Jul 27, 2009

  r131 (Commit dependency for internal model) committed by alex.blewitt   -   Commit dependency for internal model

  Commit dependency for internal model
• Jul 27, 2009

  r130 (Add suppress restrictions) committed by alex.blewitt   -   Add suppress restrictions

  Add suppress restrictions
• Jul 27, 2009

  r129 (Delete empty package) committed by alex.blewitt   -   Delete empty package

  Delete empty package
• Jul 27, 2009

  r128 (Delete empty package) committed by alex.blewitt   -   Delete empty package

  Delete empty package