MAJ système

Frédéric Testuz <testuz73@SANSPUBperso.ch.invalid> wrote:

On Fri, 19 Dec 2003 09:09:18 +0100, langmc@free.fr (michel langlois)
wrote:

Frédéric Testuz <testuz73@SANSPUBperso.ch.invalid> wrote:

On Thu, 18 Dec 2003 23:14:02 +0100, invalidcgallais94@nospam.free.fr
(Christian) wrote:

Ce soir c'est :
Xcode 1.1

Où ça ?

tu ouvre MàJ Logiciel, il sera proposé.....

D'accord. J'avais essayé de voir sur le site Apple. Mais je n'avais
rien trouvé. Je voulais savoir quelles étaient les modifications.

You can always get back to this file by choosing Show Release Notes from
the Help menu. Older release notes can be accessed with the Show Older
Release Notes menu item.

AppleScript Studio

New Features
? Support for setting breakpoints and stepping through
scripts is functional.
? The "Compile" menu item is enabled for AppleScript
files.

Current Known Issues
? You cannot stop at breakpoints in a script or step into
a script that is loaded with the standard addition load script.
? The debugger may not stop at a breakpoint on a will open
handler or on other handlers that are executed very early in the launch
process.
? Changing a variable's value while debugging will cause
the variable to become a string.

Building

General Improvements
? Command Line Tool Fixes
? The -buildstyle option for xcodebuild is honored.
? agvtool works properly on .xcode project files in
addition to .pbproj and .pbxproj files.
? Project Model Fixes
? An entire project can be upgraded at once to use native
targets.
? When creating a new native target (or upgrading a
classic target to native), the associated Info.plist file is added as a
reference to the project. If SCM is currently active the file is also
marked to be added to the SCM repository.
? You can set a specific file type for any file using the
file reference inspector.
? Support for per-platform variants has been removed.
? Target Fixes
? Aggregate targets can contain a Shell Script build
phase.
? The 'Shell Script' target template no longer creates an
associated executable.
? 'Legacy Makefile' targets are called 'External Targets'
and use the classic target editor.

Classic Build System Improvements
? The build system has a new build setting,
JAVA_FORCE_FILE_LIST, that allows the user to force the Java build to
use the@includefile path in the Jambase.
? There is user interface for setting javac's -source
flag.
? Restored ability to create "classic" versions of various
targets (Application, Framework, Bundle, Library, Tool).
? Warnings and errors for Java builds should get properly
cleared out on a rebuild.

Native Build System Improvements
? New Features
? Implemented initial support for robust precompiled
headers by generating them on-demand for each combination of source
header and permutation of compiler flags. A side benefit is that
precomps of a particular header with a particular set of flags can be
shared across targets. The size of the cache used to store the shared
PCH files can be controlled by setting
theBuildSystemCacheSizeInMegabytes default. See the Expert Preferences
notes for more info.
? Initial support for building kernel extensions (KEXTs)
using the native build system.
? Build Phase fixes
? Fixed some problems with Copy Files build phases not
copying to the proper locations inside bundles.
? Fixed problems with copying files to an absolute path
via a Copy Files Build Phase.
? Build Setting changes
? The following GCC flags or build settings have been
added to the 'GCC C/C++ Compiler' collection:
? "Sign Comparison" (-Wsign-compare)
? "CodeWarrior-Style Inline Assembly" (-fasm-blocks, GCC
3.3 only)
? "Enable Objective-C Exceptions" (-fobjc-exceptions, GCC
3.3. only)
? "Assume Non-nil Receivers" (-fno-nil-receivers, GCC 3.3
only)
? "Other C Flags" (OTHER_CFLAGS)
? "Other C++ Flags" (OTHER_CPLUSPLUSFLAGS)
? "Other Warnings Flags" (WARNING_CFLAGS)
? The following build settings have been added to the
'General' collection:
? "Info.plist File" (INFOPLIST_FILE)
? "Product Name" (PRODUCT_NAME)
? "Installation Path" (INSTALL_PATH)
? "Symbol Ordering Flags" (SECTORDER_FLAGS)
? Descriptions for GCC and Rez settings that correspond to
a command-line option also contain the name of that option. This makes
it easy to filter the options based on the literal flag name.
? Fixed the "Library Style" build setting so it shows up
properly.
? Fixed the "Effective C++ Violations" compiler setting
(the wrong flag was listed).
? Added the "Compile Sources As" compiler setting, which
tells GCC to ignore a file's extension and treat all source files as a
specific file type.
? The various *ROOT build settings can be defined in terms
of the home directory by using the ~ shorthand (e.g. ~/Binaries).
? Language-specific and/or compiler-specific options are
supported. All language-specific settings are still shown in the build
settings table, but compiler-specific settings are only present when the
proper compiler is selected.
? The native build system looks at the CC and CPLUSPLUS
flags when determining the path of the compiler for C/Objective-C and
C++/Objective-C++ files, respectively. It also looks at LD and
LDPLUSPLUS when linking. If any of these build settings are defined,
they override the compiler and linker paths that would otherwise have
been chosen. This is done for compatibility with Project Builder and
with common makefiles.
? When upgrading a target from classic to native, the
warning flags in "Other C Flags" and "Other Warnings Flags" are no
longer mapped into the more specific warning build settings. This change
was made to ensure that the semantics of the imported warning flags are
preserved.
? The UNSTRIPPED_PRODUCT build setting is now obeyed.
? General Fixes
? When building against an SDK with GCC 3.3, Xcode treats
$(SDKROOT)/usr/include as a system header directory.
? Added support for dependency analysis warnings & errors.
? The native build system uses gcc instead of g++ for
compilation (g++ is still used for linking) to avoid problems generating
PCH files.
? Per-file build settings no longer "stick" around for
those files that have no per-file build flags.
? When a target's build settings change, recompute its
product reference's name if necessary.
? Search paths are no longer ignored when using SDKs
? Added new project templates for static and dynamic
libraries.
? Native targets with names containing non-ASCII
characters no longer fail to build.
? For native targets, we make sure that the dependency
graph gets updated if any of the includes need updating.
? Custom strip flags work when Zero Link is not enabled.
? Improve the speed of creating the headermap (especially
when on NFS).
? Fixed some potential deadlock issues when running
predictive compilation combined with normal builds.
? Fixed problem where code completion could cause
predictive compilation to fail.
? Predictive compilation is turned off when the computer
is running on battery power.
? Xcode properly notices changes to .r files.
? Adding a #include to a source file immediately changes
the dependency graph.
? Precompiled headers are recompiled after changes to
header included by prefix header.
? Linking one static library into another static library
works properly.
? When using a copy files phase to copy into the
$(TARGET_BUILD_DIR), during installs Xcode will not prepend
$(INSTALL_ROOT) since it's already been prepended earlier. This avoids
bogus paths which can break (for example) embedded frameworks.
? Shell script build phases are no longer run in parallel
and sometimes out-of-order.
? A warning is displayed when Xcode comes across a file in
a Sources build phase that has no associated compiler.
? The USE_HEADERMAP build setting can be used to turn off
headermaps for a native target.

Shell Script Build Phase Inspector Improvements
? It is much easier to add and remove input and output
paths.
? The "plain text" syntax coloring font setting is used
for the script text.

Target Inspector Improvements
? 'General' pane fixes
? The Target inspector displays the full product name and
identifies the type of product (e.g. Application) that it produces.
? The outline view for selecting new dependencies show all
possible targets and those that have already been chosen are disabled
and not selectable.
? The return and delete keys add and delete target
dependencies.
? 'Build' pane fixes
? Only custom build setting names are editable.
? The help text was not being updated after filtering the
build settings table. This could have led to the wrong help showing for
the currently selected option.
? The build settings table will update the set of
available build settings when the dependency graph has been updated.
? The build settings table should properly end editing
with Tab and Return.
? The 'Escape' key will cancel editing.
? When a new custom build setting is added or a custom
build setting name is changed, the proper cell is selected afterwards.
? Duplicate build settings are no longer displayed when
selecting multiple collections.
? The per-file build settings inspector is only available
for source code files.
? 'Rules' pane fixes
? You can delete the first user-defined build rule created
in the 'Rules' tab.
? The dependency graph for native targets is properly
updated when editing build rules that use custom scripts.
? 'Properties' pane fixes
? The 'Properties' tab in the Target inspector is only
shown for native targets that have an Info.plist.
? The image for the application icon updates once the icon
name has been changed.

User Interface Improvements
? Build Results Window Fixes
? Greatly improved responsiveness of the 'Errors &
Warnings' smart group and when displaying large numbers of errors and
warnings.
? The preferences for opening and closing the build
results window automatically work.
? The available set of toolbar items has been greatly
enhanced (active target, active build style, active executable, project
window, and more).
? The state of debugging symbols is properly displayed in
the target build messages.
? Build Status Fixes
? Better feedback is provided as to whether there are any
errors, warnings, or both.
? Better feedback is provided when 'Check Syntax'
completes.
? General Fixes
? If you quit in the middle of a build or debug session, a
sheet pops up asking if this is okay.
? The "Classic" target editor and executables editor shows
up in the embedded editor when a classic target or executable are
selected.
? 'Continue to build after errors' works for the currently
building target (the build will stop at the end of the first target that
has errors)
? You can duplicate a target or executable.
? Added menu item to stop an ongoing build.
? 'Edit Active Target' and 'Edit Active Executable' menu
items have been added.
? Double-clicking on a native target brings up a Get Info
window on the target.
? Project Window Fixes
? You can set the public/private status of a header (or
multiple selected headers) in the detail view.
? There are preferences to have the Errors & Warnings
smart group become visible when a warning or error occurs.
? Added contextual menu items for adding a new build phase
to a target. If no target is selected the build phase is added to the
active target.
? javac errors and warnings show up in the "Warnings and
Errors" smart group.

Current Known Issues
? Currently Java and AppleScript files are not supported
in native targets, and therefore targets containing these languages
should not be upgraded to native. The target upgrading sheet has been
updated to point this out.
? Development builds should not use the -sectorder flag.
Using the -sectorder flag may expose an issue with symbol generation
which causes GDB to treat all variables as out of scope. Developers who
experience this problem can remove use of the -sectorder flag as a
workaround.
? To turn off Zero Link you must edit the "Development"
build style ? bring up the project inspector, click on the "Styles" tab,
select the "Development" build style, and uncheck the "Zero Link"
setting.
? How Zero Link relates to other linking options may not
be clear from the user interface. With Zero Link, linking is done at
runtime and is available only for development done from within Xcode. It
cannot be used for linking of products that are to be run outside of
Xcode.
? Options for linking with a two level or flat namespace
are not available in the user interface, but work with Zero Link. To use
these options it is necessary to manually add linker flags to the "Other
linker flags" build setting that is with the linker settings in the list
of standard build settings.
? Prebinding is incompatible with Zero Link. Although the
prebinding option appears to always be available in the user interface,
this option is ignored when Zero Link is being used.
? In classic targets, it was sometimes the case that a
build setting needed to be quoted when it was entered in order for the
target to build correctly. For instance, the PREFIX_HEADER setting might
have required quoting. In native targets, it is generally the case that
these settings should not need to be quoted, particular if the setting
represents a file name or path. Xcode does not provide an automatic
mechanism for dequoting or handling such quoted settings, so users
should be aware when they upgrade a target to native that they may need
to manually dequote some build settings in order for their target to
build correctly.
? The build options that are shown in the inspector for
build styles apply only to native targets. If a project contains classic
targets, the same build settings as those used by Project Builder can be
added in the Current Settings collection in the inspector. See the Xcode
build settings release note for more information.
? During a shell script build phase the error "** INTERNAL
ERROR: Uncaught Exception ** Exception: didn't find classname for 'isa'
key" results from calling 'pbxbuild' in the shell script. Change
invocations of pbxbuild toxcodebuild in shell script build phases.
? Cross-development settings work only with "native"
targets, not with "classic" targets. Because some code models (e.g. Java
and AppleScript) cannot yet be built with native targets,
Cross-Development can't be used to develop for those code models.
? Because Mac OS X 10.1 does not support weak-linking, you
cannot use the 10.2 or 10.3 SDKs when the Mac OS X Deployment Target
setting is set to 10.1. If you set the deployment target to 10.1 and use
APIs from 10.3, the resulting code will load only on 10.3, and will not
load on either 10.1 or 10.2.
? GCC 3.3 cannot be used with the 10.1 SDK.
? Predictive compilation can yield unexpected build
failures when there are unsaved changes in files used during that
compilation. One way this can happen is if a header file is changed but
not saved, and the corresponding implementation file is changed and
saved. When the implementation file is saved it is predictively
compiled, but the version of the header which is saved on disk is used.
This may result in a compilation failure. This failure is cached, but it
is not displayed immediately. Later, when a build is performed the
header will be saved, but the cached failure will be presented even
though all the files on disk might now compile successfully. To work
around this issue, simply touch the implementation file and recompile
it.
? You can only distribute builds to computers that have
Xcode 1.1, and the same system and compiler versions. For example, if
you are running on Mac OS X 10.3.1 with GCC 3.3 and Xcode 1.1 then you
can only distribute builds to machines that have the same configuration
(Mac OS X 10.3.1, GCC 3.3, Xcode 1.1).
? ZeroLink currently does not support C++ template based
singletons. C++ views each ZeroLink .o file as a separate shared library
and C++ does not coalesce template instantiations across shared
libraries.
? lex and yacc are not supported in the native build
system. Targets that need to use lex or yacc should use classic targets.
? The current version of distcc doesn't properly parse
-x<language>, which leads to either distcc silently failing over to
build locally or hard errors when using PCH. To workaround this problem
use -x <language> (for example, use -x c++ instead of -xc++).

Code Sense

New Features
? The indexing system for Xcode 1.1 now supports the use
of indexing templates -- the ability to populate an initial project
index with a pre-cooked "template". This can greatly speed up the
initial indexing for a new project and the reindexing of an existing
project. This functionality is not enabled by default; for more
information on how to install and enable the templates, see the in-depth
documentation in the/Developer/Extras/Xcode Index Templates/Index
Templates ReadMe.rtf file.
? The Xcode 1.1 release now contains a command-line
indexing tool, called "xcodeindex" (installed in the same path as
"xcodebuild", /usr/bin). This tool allows you to perform a number of
symbol indexing related tasks on a project from the command-line. The
basic usage is:
?
xcodeindex [-project projectname]... [-quiet] [-loglevel level]
[indexaction]...
?
The options for the command are:
?
-project Allows you to specify the name of a project to index, should
the command not be invoked from inside the project directory itself.
This behavior mimics that of the 'xcodebuild'.

-quiet Turns of all logging output for the indexing process.

-loglevel Turns on varying degrees of indexing debugging. The level
range is from zero to six, enabling a staggered number of the existing
indexing defaults for the indexer. (If an option greater than six is
used, then the maximum level of logging is enabled). The logging level
values are defined as:

?
0
No logging (like -quiet)

?
1
Prints the name of the file being indexed [DEFAULT]

?
2
File processing output

?
3
Symbol updating output

?
4
Symbol insertion and creation output

?
5
Parser basic output

?
6
Parser error output

The levels are inclusive -- thus enabling log level 4 would also
automatically include levels 1,2, and 3. This output from the logging
(above level 1) is not expected to be useful for most developers, but
could be valuable in troubleshooting cases where there is a problem with
indexing a particular project.
The indexing actions currently supported are:
?

?
clean
Removes the index for the project

?
build
Updates the index for the project (creating, if necessary) [DEFAULT]

?
rebuild
Removes, then re-creates the index for the project

?
stats
Prints the statistics for the index (number of classes, etc)

?
dump
Dumps a tab-delimited format of the index (for major symbols -- classes,
methods, etc) to stdout
?
If no action is specified, the command assumes a "build" action.

For example, if you wanted to clean a project, you would invoke the
command (from inside the project folder):
xcodeindex clean
?
If you wanted to build three projects with no logging, you would invoke
the command (from the parent folder for the projects):
?
xcodeindex -project FirstProject -project SecondProject -project
ThirdProject -quiet
? A setting now exists to specify a default location for
the index for all projects (rather than in the intermediates ("Build")
folder of the project). This is a per-user setting, not a per-project
setting, so all projects will use the path specified in the setting to
store their indices. (Thus, if a value is set and two versions of the
same project are opened, they will both use the same index). To set the
base path for the indices, simply set an absolute path as the value for
the PBXCodeSenseIndexBasePath default.
? Xcode offers two kinds of completion -- string-based
completion, which returns the list of matching words from the file, and
symbol-based completion (also known as 'code completion'), which returns
the list of matching symbols for context of the current insertion point.
(The keystrokes to invoke these items can be configured in the Key
Bindings preference panel.) Now in Xcode 1.1, the string completions are
included in the list of options when using the code completion. These
items will appear in with the other symbols (discernable by the lack of
a 'type icon' in the first column in the pop-up display), and can be
inserted just like the other symbols. (If you prefer to only have the
symbols in the list and not include the strings, you can set the
PBXCodeSenseExcludeStringsFromCodeCompletion default to YES and they
will be omitted).

Indexing Improvements
? The "Rebuild Index" button from the alert panel (brought
up when there is an exception while indexing) now properly removes the
old index and starts indexing.
? The "Enable Indexing" item in the Navigation preference
now updates the current state of all projects (such that if you turn off
the indexing preference, all projects currently being indexed will
cease).
? Crashes that sometime occur after starting a build with
indexing enabled have been fixed.
? The File Reference inspector now displays an "Include in
index" checkbox for excluding .jar files and folder references from the
index (mainly useful for Java projects).

Class Browser Improvements
? The class browser always opens the declaration for a
symbol (class or method), rather than the definition. The definition for
the symbol can be seen by holding down the option key when clicking
(either single or double) on a class or method.
? A contextual menu item has been added for creating a
bookmark (in the Bookmarks Group) for a class or method.
? 'Reveal in Class Browser' works in source files.

Code Completion Improvements
? Code completion is much faster at displaying large lists
of potential completions.
? Dangling completion ellipses ('?') left in source code
after using code completion no longer occur.
? The code completion menu shows up properly on secondary
monitors.
? For all non C-based languages (that have syntax
coloring), the auto-completion list includes all words in the current
file.
? The Navigation Prefs pane includes options to customize
the delay afterw which code completion pops up automatically.
? The keystroke to "Jump to next placeholder" will work
anywhere in the file and will cycle through all of the placeholders (not
just those on the same line as the cursor).
? Page-up and page-down work properly in the
code-completion list, and the completion list cancels for mouse events
in other windows.
? When no match is found during (manually requested) code
completion, Xcode provides feedback (in the form of a popup).

Current Known Issues
? When a file is first encountered while using Code Sense,
there may be a short pause as the file is processed.
? Code Sense relies on a proper filetype identification
for best results (i.e. .c files that are actually C++ files will not
fare well).
? Code Sense is not supported for Java or CocoaJava.

CodeWarrior Project Importer

General Improvements
? You can attempt a re-import of the same project without
quitting Xcode.

Current Known Issues
? For best results when importing we suggest the
following:
? Leave Xcode alone while the CodeWarrior project is being
imported.
? Only import one project at a time.
? Close all open CodeWarrior projects and quit CodeWarrior
before starting the import.
? A successful import does not imply that your project
will build successfully, since (by design) the importer does not modify
source files.
? Be aware that the importer was designed with CodeWarrior
Pro 8.3 in mind, so the farther you deviate from this version, the less
accurate the import may be.
? It may happen that an AppleScript or CodeWarrior error
occurs during the import. In this case, the best thing to do is to check
the Console for details and trying importing again. If an import fails
repeatedly, please file a bug with as much detail as possible.
? With this release, intermittent cases have been reported
of CodeWarrior AppleScript errors while importing (error 9 - target not
found). The reasons for this error are not fully understood at this
point, but launching the project that fails to import under CodeWarrior
Pro 8.3 seems to help.
? The importer does not currently support bringing in CW
Targets that use the Java Linker or the Mac OS Merge Linker.

Customization

General Improvements
? Additional support files for Xcode are located inside
the "Library" domain in Application Support/Developer Tools/Apple/. Look
at /Library/Application Support/Developer Tools/Apple/ for examples of
the kinds of support files possible.
? See the "User Interface" section for more information on
improvements to remembering window state.
? See the "Building" section for more information on
customizing the behavior of the Build Results window and Errors &
Warnings smart group.

User Scripts Improvements
? The User Scripts menu is installed in Xcode's main menu
by default. Previously, you had to install a start-up script and user
scripts folder in~/Library/Application Support/Apple/Developer Tools
before the menu would appear. The default user scripts menu makes use of
the StartupScript script and Scripts folder in /Library/Application
Support/Apple/Developer Tools. You can override the default start-up
script or Scripts folder by placing your own implementation of either or
both of them in ~/Library/Application Support/Apple/Developer Tools.
? The User Scripts menu item, by default, displays a icon
rather than a textual title. The icon is provided by a file named
menuIcon.tiff, which is located in the Scripts/10-User folder. In fact,
any top-level folder within the Scripts folder can include
amenuIcon.tiff file to provide an icon for inclusion in Xcode's main
menu.

Note: This feature required changes to both Xcode and to the default
start-up script. If you already have a copy of StartupScript
in~/Library/Application Support/Apple/Developer Tools, you will need to
replace it with a fresh copy of/Library/Application
Support/Apple/Developer Tools/StartupScript for the menu icon to appear.

Debugging

New Features
? Xcode supports a "disassembly view". If there is no
source code for the current frame, we show the disassembled code. The
user can also swap between source, disassembly only, and a split view
with both using the debug menu item 'Disassembly display' to toggle the
three states. When disassembly display is disabled we still show
disassembly when you select a stack frame that has no symbols, however
the registers are not displayed. If you turn on disassembly display for
a frame you are already in then the 'Registers' item will not display
until you step the debugger. Registers entered in the Expressions window
will display immediately.
? The Variables Pane has a 'Registers' item when you
enable disassembly display in the debug menu that shows the current
state of all registers. The expanded state of the registers is currently
not remembered. If you want to watch a specific set of registers use the
Expression window from the debug menu 'Expressions...' and enter the
expression as '$r0', '$pc' etc then change the display format using the
contextual menu. The display format is not remembered across debugging
sessions in the Expressions window.
? Xcode has a menu item and toolbar item for 'Step
Instruction'.
? Added support for 'Continue to Here'. Option-click in
the gutter to continue to the clicked line.
? Breakpoints are labeled with the function they are in
(i.e. foo: - Line 13), If no function name can be found, we fall back to
the old format (foo.m: 13).

Debugger Improvements
? Hangs while processing significant STDIO output in the
console have been eliminated.
? Hitting breakpoints always results in either source code
or disassembly being shown in the debugger window.
? The debugger brings up a sheet if you attempt to quit or
close the project while debugging.
? finish and return work in the GDB console.
? When fixing a file, the debugger was sometimes trying to
set the PC outside of the current frame.
? The debugger properly handles exceptions during
introspection.
? The console window for the debugger resizes itself
if it
is opened off-screen.
? Typing ^C in the GDB console will interrupt the
executable.
? The debugger split position is remembered.
? By default, standard I/O uses a pseudo terminal when you
run an executable.
? Setting a symbolic breakpoint on an overloaded function
no longer causes UI debugger to "hang". Xcode shows the breakpoint as
disabled when there are multiple matches; users must use the console to
set a breakpoint on a symbol with multiple matches.
? When closing the debugger window, Xcode no longer closes
associated windows.
? When using external editors for a given filetype, files
of that filetype still show up properly in the debugger window.

GDB Improvements
? 'info mach-regions' works correctly.
? New 'sharedlibrary specify-symbol-file index' command
makes it much easier to add symbols for an already loaded shared
library. The index is just the index from the output of 'info
sharedlibrary'. GDB will take care of making sure the symbols are mapped
in at the correct location even if your library has slid.
? The command 'info sharedlibrary address' shows the
library that was mapped in at a given address. The info it displays
includes the index used by the specify-symbol-file command, so you can
use this to figure out what library to add to get symbols for addresses
you find in a backtrace, for instance.
? Fixed some cases where breakpoint commands that
continue'd the inferior would crash GDB.
? Fix & Continue handles more corner cases.

Variable Display Improvements
? The debugger does a better job of distinguishing between
nil and "Invalid" objects.
? Items not at the top level of the variables pane are
auto-expanded more consistently.
? You don't need to restart Xcode to change or install new
data formatters.
? Private members are more consistent about showing
summary info.
? The data formatters support unions better.
? Escape cancels editing in the variable display pane.
? OSType variables with a value of 0 show up as 0 (before
they would just be blank).

Symbolic Breakpoints
A symbolic breakpoint created in the GUI while debugging will be
automatically disabled if there are multiple matches for the symbol.
Either enter the canonical, full name, of the symbol or set the
breakpoint in the console then interactively choose which one to break
on. If an ambiguous symbols is enabled before starting a debug session
and ZeroLink is enabled then a breakpoint will only be set on the first
symbol that matches. If ZeroLink is disabled then the breakpoint will be
disabled to indicate there are multiple matches. For example, if you
have the overloaded functions'A::do_it(int)' and 'A::do_it(int,int)' you
can specify 'A::do_it(int)' and 'A::do_it(int,int)' as symbolic
breakpoints in the breakpoints panel. If you enter 'A::do_it' then there
are multiple matches and the breakpoint will not enable. You must either
be more specific or use the console if you wish to break on all
instances.

Current Known Issues
? In some cases, when starting up GDB, you may see a
number of error messages of the form:
warning: Version for symbol file "/usr/libexec/gdb/symfiles/QD.syms" (5)
does not match version for GDB (6); ignoring.
You can remove these warning by opening a Terminal window and invoking
the command

sudo /usr/libexec/gdb/cache-symfiles
? A Fix and Continue operation that fails with a message
like
"GDB: Error fixing SKTGraphic.m: Bundle
'/private/tmp/EF158D230493E3A3100C91692' not found"
usually means the build of the fix bundle failed. Check the Errors and
Warnings smart group, detailed build log and annotated gutter of the
source editor for build errors.
? Adding a symbolic breakpoint in the GDB console will not
create a breakpoint in the Breakpoints panel or add it to your Project.
GDB will still use the symbolic breakpoint.
? Symbolic breakpoints in the Breakpoint panel cannot be
renamed. The workaround is to add a new one.
? If the debugger GUI gets out of sync with GDB choose
'Sync with Debugger' in the 'Debug' menu to recover. Please file a bug
report for any reproducible cases at http://bugreport.apple.com.
? When debugging a ZeroLink application with GDB the first
attempt to step into a function or method in a ZeroLink bundle that has
not been loaded yet will step over the function. Subsequent attempts to
step into functions contained in that bundle will succeed. The
workaround to step into a function that has not been loaded yet is to
set a breakpoint in the function or method in Xcode, setting a future
breakpoint on the function or method name or setting a file and line
number breakpoint.
? In some cases you may find the run log does not display
all the text you are expecting. Likely you need to change how Xcode is
communicating with the tool from 'Pipe' to 'Pseudo terminal'. Double
click the executable in the Project window to get the Executable
Configuration window. Scroll down to the Launch Configuration section,
choose 'Run action' in the 'Configure' popup, then choose 'Pseudo
terminal' in the 'Std In/Out' popup.

Documentation

General Improvements
? Bringing up the documentation window is bound to
Command-Option-?
? Option-double-click always brings up the documentation
window. The document corresponding to the first match is loaded
automatically.
? Option double-click searches no longer reset the
documentation group to 'Library', but search against the currently
selected group.
? Option double-click searches cancel any running
searches.
? There are two new contextual menu items to bring up
documentation: "Find Selected Text in Documentation" and "Find Selected
Text in API Reference".
? The documentation window remembers its state, including
the selection in the Groups list, last search type, split bar positions,
and configuration of the table views.
? The documentation window honors Xcode's list font.
? When travelling to a new page, the page up and page down
key, as well as the Find and Print commands, work without having to
click in the displayed file.

Editor Improvements
? The symbol popup stays in sync with the documentation
shown in the editor.
? The symbol popup in the documentation window lists the
top-level headings of the document (H1 and H2 headings) along with the
symbol names.
? Documentation file editors provide a contextual menu,
which includes these commands: Open Frame in New Window, Open Link in
New Window, Open Link in Browser, Copy Link to Clipboard, and Copy Image
to Clipboard.

Searching Improvements
? You can sort the found symbols list in the documentation
window by clicking any of the column headings.
? The accuracy of relevance rankings for API documentation
has been improved.
? Tools documentation is properly indexed and used in
documentation searches.
? For API searches, the current search string and the
search results always stay in sync.
? Tooltips have been added to the search results table.
? Searches of the 'Tools' documentation set search Xcode,
Interface Builder, and FileMerge help books along with the Tools
documentation.
? Sections 9 and 'n' are searched along with 1-8 when
searching man pages.

Current Known Issues
? The developer documentation released with Panther (Mac
OS X 10.3) had a problem that prevented full-text searches of the Tools
group in the documentation window from finding anything outside of the
release notes. Thus, search results from the Xcode, gcc, make, and
related tools documentation were never returned. To enable searching of
the primary tools documentation, run this command in a Terminal window:
sudo ln -s /Developer/Documentation/DeveloperTools/DeveloperTools idx
/Developer/Documentation/DeveloperTools/Tools idx

In subsequent releases of the developer documentation, this problem has
been solved. (If/Developer/Documentation/DeveloperTools/Tools idx exists
on your system, there's no need to run the command above.)
? By default there is limited access to Java API through
the "Quick API" search facility or through Option double-clicking a
symbol in a code editor, since most of the Java documentation is shipped
in a jar archive and so is not indexed. To make the documentation
accessible, run this command in a Terminal window:
sudo /Developer/Documentation/Java/scripts/unjarJavaDocumentation.sh

This script extracts the documentation from the jar archive and runs
/Developer/Tools/pbhelpindexer on the resulting HTML files to index
them.
? The 'Xcode Help' documentation has the following
shortcomings:
? Screenshots of the project window show an older icon for
the action pulldown.
? The section "Converting a Project Builder Target" does
not describe the 'Upgrade to Native Target' menu item.
? The contents of each chapter in 'Xcode Help' are always
disclosed in the Table of Contents.
? Text in the "Formatting Code" section of the "Editing
Files" chapter is blue.

File Editing

New Features
? The default tab width for new users has been changed to
4 characters. And the default behavior is to insert tab characters
instead of replacing them with spaces. Users who have never changed from
the old defaults may need to change them with this update. This is done
in the Text Editing Preferences pane.
? The navigator bar has popup menus for the bookmarks and
breakpoints in the current file. Similar to the function popup, these
menus will scroll to the selected bookmark or breakpoint in the current
file.
? The navigator bar supports "symbolic counterparts",
which will take you to the symbolic counterpart (definition or
declaration) for the class, method, or function currently selected (or
that the cursor is in) in the file. To use this, hold down the option
key when clicking the "Go to Counterpart" button in the navigation bar.
Additionally, a key-binding can be set for this functionality using the
Key Bindings preference (under "Text Key Bindings -> Navigation").
? We provide a header (file name) and footer (timestamp
and page number) when printing source code. We also make sure the print
job is properly labeled.
? Added Balance command to the Format menu and the text
editor's contextual menu. This is bound to Cmd-B when using CodeWarrior
or BBEdit key bindings.

Indentation Improvements
? Shifting text left or right no longer trounces the
previous formatting.
? Auto-indentation deals properly with Mac line endings
(CR).
? Auto indentation properly handles colons in C++ and
ObjectiveC code.
? Auto-indentation and tabs work together better.
? You can manually override auto-indentation.
? Indentation works properly when code completion is on.
? Line wrapping wasn't getting the indent quite right for
proportional fonts.
? "Insert Open Brace" has been added to the set of text
bindings. This allows users with international keyboards to change the
binding for the '{' key on their keyboards. The correct binding is
required for the "Insert matching brace" preference to work.
? Syntax-aware indentation is no longer active in string
literals or comments.
? Re-indent is available when smart indentation is turned
off.

Navigation Bar Improvements
? The function popup is not confused by conditionals as
much.
? The function popup displays the same images as the class
browser.
? The column location shown in the file navigator properly
counts tabs (using the tab width setting).
? Added a "Clear File History" menu pick to bottom of nav
bar file list.

Performance Improvements
? Text layout and file loading is marginally faster for
simple source code, but up to 8x faster for certain cases.
? Performance while editing large files has been greatly
improved.
? Improved performance when displaying multiple warnings
and errors in the gutter for a given line.
? Opening a file with a large number of warnings and/or
errors is vastly improved (up to 50x).
? Improved scrolling speed in open editors.
? Added caching of the global symbols queries in between
updates, so code completion should be much snappier for general usage
(as much as 5x faster).

Syntax Coloring Improvements
? Improved syntax coloring for Ruby.
? Added syntax coloring and function popup support for
Dylan.
? Jam rules and actions have different icons in the
function popup.
? Improved syntax coloring for JavaScript.
? By default, plain files are no longer syntax colored,
set XCColorUnknownLanguages to YES to get the old behavior.

Text Editing Improvements
? Changes to tab settings are reflected immediately in any
open files.
? We no longer spuriously jump to the end of the file
sometimes when the user is pressing the down arrow while editing the
file.
? Fixed a well-known (but hard to reproduce) crash on undo
after pasting text.
? 'Home' and 'End' keys no longer move the insertion
point.
? Xcode no longer strips the BOM tag from UTF-8 files.
? Errors and Warnings markers (in the gutter) should stay
with the proper line when the file is edited.
? Improved command-double-click behavior ? we attempt an
exact match search and add any ':' to the right of the selected text to
the search. This should decrease the number of matches and make it more
accurate.
? Double-clicking '<#' or '#>' selects the entire argument
placeholder.
? Double-clicking on a " or a ' selects the contents of
the quotes.
? We have a new default XCSelectToInsideMatchingQuotes
which overrides the behavior specified with the "Select to inside
matching braces" preference.

User Interface Improvements
? If we can't read a file, we put up an alert and allow
the user to pick another encoding to try.
? You can set XCShowUndoPastSaveWarning to NO to turn off
the "undo past a save" warning sheet.
? The last size and position of the separate editor window
is remembered (if the editor checkbox is set in the "General
Preferences" pane).
? When using external editors for a given filetype, single
clicking on a file of that filetype will show the file in the attached
editor.
? The bookmark name for a text selection defaults to the
selected text (if there is a selection).
? All navigators properly restore their loaded files. In
particular, separate editors only list the files opened in that editor.
? Scroller marks are shown for errors/warnings.
? 'Next Build Result' and 'Previous Build Result' are
supported in the editor (cmd-+ and cmd-=).
? "Swap With Mark" repositions the window to the mark
location.

Current Known Issues
? Currently, separate editor windows only support one
split (horizontal or vertical). A vertical split can be created by
option-clicking the split control.

Find

New Features
? Added ability to search arbitrary sets of files and
folders, just the currently selected files, and/or a set of files based
on a regular expression.
? The 'Find In Project' window shows an outline view for
the find results (which can be hidden via a disclosure triangle).
? Double clicking a find result opens the 'Find In
Project' panel and synchronizes the search options UI with those used
for the find result.
? Previous finds can be re-run again later.

ProjectBuilderWO Project Importer

Current Known Issues
? The import will fail if an Xcode project already exists
in the project directory. If you want to re-import a PBWO project,
remove the existing Xcode project and then perform the import.
? Projects imported from PBWO use classic targets.

Source Code Management

New Features
? Basic support for 'cvs annotate' has been added.
Currently you can only act on the checked out file and the raw results
are placed in a new untitled window. No Perforce support as of yet since
Perforce doesn't have a comparable command.
? An SCM smart group has been added to the project window.

CVS Improvements
? Update respects if a file is currently on a branch.
? Status on a file no longer reports bogus errors (i.e. it
no longer thinks that error strings in the message log text are really
errors).
? SCM understands log messages that start out with a blank
line.
? Improved support for SSH authentication with
passphrases.
? The sticky tag is no longer removed after update
operations.

Performance Improvements
? We no longer request SCM status for a group's content
when expanding it.
? Ongoing SCM operations are cancelled when SCM is turned
off.
? SCM status operations no longer occur when warnings or
errors or find results are posted during a build.

SCM Inspector Improvements
? The SCM inspector has an 'Update' button which is active
when one revision is selected. If the base revision is selected, the
button changes to 'Discard'.
? The revisions table includes a 'Date' column.
? Long revision numbers are not cut off (this was
particularly bad with branched files).
? URLs in log messages are clickable.
? We only show the SCM inspector for the project group and
any non-bundle file reference.
? Clicking on a column header to sort the revisions table
no longer selects the column.

User Interface Improvements
? BBEdit comes to the front properly when used to perform
comparisons.
? All SCM actions that requires authentication ask for it.
? Added tooltip to SCM status in the SCM pane (to show
full description of the status?? so "M" gets the tooltip "Locally
modified", etc)

Current Known Issues
? Xcode does not handle bundled files, such as nibs, with
Perforce.
? Xcode does not mention the changelist number anywhere.
? Only a failed connection to the Perforce server will be
reported; all other failures are completely silent.
? When using Perforce, if a Compare command launches
FileMerge, no other SCM operations will run until you quit FileMerge.
? There is no support for working offline from the
Perforce server, nor for re-syncing when you go back online.
? When you diff or annotate a file, if you want to diff or
annotate the file again against the same revision, you have to close the
editor or window containing the original result before the new operation
will complete successfully.

User Experience

New Features
? An Action toolbar item is available for the Project
window and in separate editors which provides a context menu over the
current selection as is found in Panther's Finder.
? A "Configuration History" toolbar item is available for
the Project window which allows the user to move backward and forward
from one configuration to another.
? The View menu has menu picks and a keyboard equivalent
to show/hide the embedded project editor.
? The current Build State is displayed on the right hand
side of the status bar in applicable windows. This build state will be
blank until a build is performed. During a build, icons for errors and
warnings will appear in the right hand side of the status bar when they
are detected in the build. You may click on these icons to display the
Errors & Warnings Smart Group. Once a build is completed, a status
keyword (Succeeded, Failed, Canceled) will appear as well on the right
hand side of the status bar. You may click on this keyword to open the
Build Results window.

Detail View Improvements
? The Detail view supports a fully functional context
menu.
? In the detail view, localized files display as 'filename
(variant)'.
? A double-click in the detail view no longer opens the
embedded editor in addition to a separate editor.
? Filtering the detail view is much faster.
? Fixed the case where the detail view would not notice
that a file had been deleted from outside of Xcode.
? The state of saved files are updated properly in the
detail view.

Filetypes Improvements
? Xcode is aware of .scriptSuite and .scriptTerminology
files
? Xcode supports the idea of file types that require tabs
(like makefiles). This can still be overridden in the File Reference
inspector pane.
? Xcode can differentiate between XML and old-style
plists.
? Double-clicking on a nib file will always load the file
in Interface Builder.
? 'Open As' works properly with files of file types that
are unknown to Xcode but externally claimed.

Groups & Files Improvements
? The Groups & Files view supports a fully functional
context menu regardless of where the user clicks.
? The state of the Groups & Files view is preserved
between sessions (if the "Save project window states when closing"
preference under "General Preferences" is checked), including the
expanded nodes, current selection, etc.
? We no longer allow you to drag files into smart groups.
? You can remove any custom smart group (like 'NIB
Files').
? The "Reveal in Group Tree" menu item shows the original
file in the project hierarchy (not its listing the the Errors and
Warnings smart group).

Inspector Improvements
? Sometimes the inspector would get confused about whether
the detail or group view was being inspected.
? The File Reference inspector is better about disabling
parts of the panel that are not applicable to the selected items.
? Inspectors that are focused on a localized file display
'filename (variant)' instead of just 'variant' for the filename.
? The localization buttons in the file reference inspector
are dimmed for frameworks and other bundles.
? You can't add a localization to a file without first
making the file localizable.
? When using an inspector to change the path that a group
points to, the group's name does not change.

Performance Improvements
? The UI handles much larger projects than before without
performance issues.
? Performance and bug fixes for state management and
navigating to bookmarks.
? Performance improvements when drawing tooltips and ruler
markers.
? Updating the Windows menu is more lazy/efficient.
? Opening the groups drawer of a separate editor with a
large number of files is much faster.

Status Reporting Improvements
? Hiding and showing status bars should work for all
windows other than the Build Results Window (which still has its own
unique status bar). Status messages will only display in windows owned
by the project for which the status message is intended.
? Status bars show a determinate progress bar rather than
the spinning wheel (where appropriate) in order to give an approximate
estimate of build progress.
? The status bar for a documentation window, class
browser, or separate editor window, provides feedback when a broken HTML
link is clicked.

User Interface Improvements
? Many issues with saving the state of the project window
have been addressed (like the state of the Groups & Files outline view
and its columns or scrolling to the last known visible region on
reopen).
? The Xcode preferences should resize more consistently
across the different panes.
? The "General Preferences" pane includes settings to
control the restoration of individual window types.
? The UI provides much better feedback when adding files,
frameworks, targets, executables, smart groups, etc. including
automatically opening editors for such items when appropriate.
? Menus and contextual menus have been updated to be more
consistent and useful. Also, tooltips are used for showing addition
information about the item acted on (where appropriate).
? You can tab (or control-tab) between the groups view,
search field, details view, and attached editor. To tab out of the
attached editor use control-Tab.
? You can hit enter to confirm the 'Save All' dialog.
? 'Open Quickly' is SDK-aware and supports framework-style
includes.
? Xcode doesn't get confused when cancelling closing a
project.
? cmd-D maps to the 'Don't Save' button in the Save All
panel.
? Saving all files when closing the project doesn't cause
Xcode to forget what files were open the next time you open the project.
? Cmd-Shift-W closes the window (or collapses the editor)
if no files are left to show.
? There is a preference in the General pane to control if
the search field is cleared when changing smart groups.
? There is a preference in the General pane to control if
the embedded editor is opened if a file is single-clicked. If this
preference is enabled we also auto-close the embedded editor if it
contains no files.
? The "Open" panel remembers the last folder location.

Current Known Issues
? You currently can not re-order smart groups.
? Dragging files from the another application and dropping
them in the "Groups & Files" view will not work correctly unless you
drop the files on the project structure itself (i.e. any node above the
"Targets" smart group). Dropping such files on any of the smart groups
will result in the display of a sheet containing no targets. Hitting the
"Add" button on this sheet will result in an error while hitting the
"Cancel" button will escape the operation and return Xcode to a valid
state.
? Splitting the 'Groups and Files' outline view (the left
hand outline view in the Project window) can cause issues later on (such
as not properly updating the 'Errors and Warnings' smart group). As a
result, one should only split this view when absolutely necessary and
then re-open the project once the used is finished with the split view.
The negative effects of this do not persist between Xcode sessions or
across open projects.

Additional Documentation and Help

Mac OS X includes developer tools such as Xcode, and it also includes
developer documentation.

Release Notes

Additional release notes for Mac OS X are located in
/Developer/Documentation/ReleaseNotes. In this folder, there are release
notes on specific tools, such as the GCC3 compiler, the GDB debugger,
and the linker, as well as on APIs (e.g. CoreFoundation, AppKit,
Foundation, CarbonCore, etc...). TheXcode Overview release note
discusses the Xcode and its role in development on Mac OS X. Be sure to
review the "Late Breaking News" section in Xcode Overview for any
last-minute information about Xcode. Also, for advanced build system
information, check the Xcode Build Settings release note.

Web Sites

? http://developer.apple.com: Apple's Developer Central
site is the best source of official up to date technical documentation
on Mac OS X as well as being the primary place to find out about
developing for the Macintosh platform.
? http://developer.apple.com/tools/xcode: The Xcode home
page on Apple's developer site.
? http://www.macdevcenter.com/mac: O'Reilly's Mac OS X
Developer web site.

Mailing Lists

There are a number of mailing lists that are great for Mac OS X and
Xcode developers. First are the Apple-hosted lists. For more information
please go to http://lists.apple.com. There are lists on the following
topics and many more:

? xcode-users: This list is great for asking (and
answering) questions about Xcode.
? java-dev: A place for Mac Java developers to hang out.
? cocoa-dev: Keep in touch with the Cocoa community.
? carbon-development: Keep in touch with the Carbon
community.
? fortran-dev: For Fortran development issues.
? unix-porting: For folks porting standard Unix software
packages.

There are also some mailing lists you cannot subscribe to but that can
be used to send feedback about various things to Apple: