mirror of
https://github.com/gnustep/libs-base.git
synced 2025-04-22 16:33:29 +00:00
New file
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@975 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
parent
e8402c57f0
commit
29048835e7
1 changed files with 45 additions and 0 deletions
45
Documentation/faq.texi
Normal file
45
Documentation/faq.texi
Normal file
|
@ -0,0 +1,45 @@
|
|||
@ifset FAQ_ONLY
|
||||
@chapter Frequently Asked Questions with Answers
|
||||
@c set the vars GNUSTEP_BASE_VERSION and GCC_VERSION
|
||||
@include version.texi
|
||||
@end ifset
|
||||
|
||||
@enumerate
|
||||
|
||||
|
||||
@item Why not separate the GNU classes from the NS* foundation
|
||||
classes?
|
||||
|
||||
They are intimately intertwinned---not in a messy way, but for good
|
||||
reasons. ...explain more detail...
|
||||
|
||||
|
||||
@item I'm trying to compile an Objective C program on Linux, and it's not
|
||||
working.
|
||||
|
||||
Link with @samp{-lieee}.
|
||||
|
||||
|
||||
@item What are the differences and improvements of the GNU base classes
|
||||
over the NS* foundation classes?
|
||||
|
||||
@itemize @bullet
|
||||
|
||||
@item Better collection class heirarchy.
|
||||
|
||||
@itemize @bullet
|
||||
@item Deep class heirarchy provides uniform method names and common
|
||||
superclasses in which to add generally-applicable new functionality.
|
||||
@item Richer use of invocations for enumerating
|
||||
@item More classes, providing new functionality, such as linked lists,
|
||||
binary trees, splay trees, etc.
|
||||
@item Dictionary can handle keys that are not Strings.
|
||||
@end itemize
|
||||
|
||||
@item Better archiving
|
||||
@item Better distributed objects
|
||||
|
||||
@end itemize
|
||||
|
||||
@end enumerate
|
||||
|
Loading…
Reference in a new issue