Author:manus

Date:2009-11-19T22:51:42.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@362 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
manus
2009-11-19 22:51:42 +00:00
parent f08c495528
commit e1e03f95b1
9 changed files with 35 additions and 13 deletions

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| FreeBSD 5.2 with either Gnome 2.6 or GTK+ 2.4. | FreeBSD 5.2 with either Gnome 2.6 or GTK+ 2.4.
|- |-
| '''C compiler'''
| gcc
|-
| '''Memory''' | '''Memory'''
| 512 MB of RAM (1GB recommended). | 512 MB of RAM (1GB recommended).
|- |-

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| HP Tru64 UNIX 5.1B with GTK+ 2.4. | HP Tru64 UNIX 5.1B with GTK+ 2.4.
|- |-
| '''C compiler'''
| HP C compiler
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| HP-UX 11 with GTK+ 2.4. | HP-UX 11 with GTK+ 2.4.
|- |-
| '''C compiler'''
| HP C compiler
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| Fedora Core 2, Slackware 10 or any Linux system with glibc 2.3 and either Gnome 2.6 or GTK+ 2.4. | Fedora Core 2, Slackware 10 or any Linux system with glibc 2.3 and either Gnome 2.6 or GTK+ 2.4.
|- |-
| '''C compiler'''
| gcc
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-
@@ -40,8 +43,6 @@ The command should succeed and the version number of GTK+ should appear. If it i
On some Linux distribution the Xtst library is required but not installed by default. You have to make sure it is installed by using the instruction of your Linux distribution. On some Linux distribution the Xtst library is required but not installed by default. You have to make sure it is installed by using the instruction of your Linux distribution.
We also require the `gcc' C compiler.
==Installing EiffelStudio from the Web== ==Installing EiffelStudio from the Web==
After downloading the installation package, you should manually extract its contents to your hard drive. For example, you can extract it into /usr/local using the following commands (assuming that you have permission to /usr/local and that the installation package was saved in /tmp/EiffelXX.tar.bz2, where XX stands for the EiffelStudio version): After downloading the installation package, you should manually extract its contents to your hard drive. For example, you can extract it into /usr/local using the following commands (assuming that you have permission to /usr/local and that the installation package was saved in /tmp/EiffelXX.tar.bz2, where XX stands for the EiffelStudio version):

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| Yellow Dog Linux 4.0 with either Gnome 2.6 or GTK+ 2.4. | Yellow Dog Linux 4.0 with either Gnome 2.6 or GTK+ 2.4.
|- |-
| '''C compiler'''
| gcc
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-

View File

@@ -6,29 +6,32 @@
{| {|
|- |-
| Computer/Processor | '''Computer/Processor'''
| G4 | x86
|- |-
| Operating System | '''Operating System'''
| Mac OS X 10.4 (Tiger) or above | Mac OS X 10.5 (Leopard) or above
|- |-
| Memory | '''C compiler'''
| gcc included in XCode
|-
| '''Memory'''
| 512MB of RAM (1GB recommended) | 512MB of RAM (1GB recommended)
|- |-
| Hard Disk | '''Hard Disk'''
| 400MB of hard disk space (1GB recommended) | 400MB of hard disk space (1GB recommended)
|- |-
| Drive | '''Drive'''
| CD-ROM or DVD drive (not required when downloading EiffelStudio) | CD-ROM or DVD drive (not required when downloading EiffelStudio)
|- |-
| Display | '''Display'''
| 1024 x 768 or higher resolution video adapter and monitor | 1024 x 768 or higher resolution video adapter and monitor
|- |-
| Peripherals | '''Peripherals'''
| Keyboard and mouse or compatible pointing device | Keyboard and mouse or compatible pointing device
|- |-
| '''ISE_PLATFORM''' | '''ISE_PLATFORM'''
| '''macosx-ppc''' or '''macosx-x86'''. | ''macosx-x86''' for x86 based CPU and '''macosx-x86-64''' for x64 based CPU.
|} |}

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| Solaris 9.0 or greater for Sparc, Solaris 10 or greater for x86 with either Gnome 2.6 or GTK+ 2.4. | Solaris 9.0 or greater for Sparc, Solaris 10 or greater for x86 with either Gnome 2.6 or GTK+ 2.4.
|- |-
| '''C compiler'''
| Sun Studio 12 C compiler
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-

View File

@@ -12,6 +12,9 @@
| '''Operating System''' | '''Operating System'''
| Windows NT/2000/XP/2003/Vista (.NET support is for Microsoft Windows 2000, XP and 2003 only). | Windows NT/2000/XP/2003/Vista (.NET support is for Microsoft Windows 2000, XP and 2003 only).
|- |-
| '''C compiler'''
| Microsoft Visual Studio 2005 or greater, or using gcc included in the EiffelStudio delivery
|-
| '''Memory''' | '''Memory'''
| 512MB of RAM (1GB recommended). | 512MB of RAM (1GB recommended).
|- |-

View File

@@ -178,7 +178,7 @@ In summary, CAPs provide void-safe protection for certain types of detachable ex
Possibly the characteristic of CAPs which is most important to developers is whether or not a particular CAP is supported by the compiler. In other words, from the developers viewpoint, the only opinion that matters in the argument of whether a particular pattern constitutes a CAP is that of the compiler. Possibly the characteristic of CAPs which is most important to developers is whether or not a particular CAP is supported by the compiler. In other words, from the developers viewpoint, the only opinion that matters in the argument of whether a particular pattern constitutes a CAP is that of the compiler.
If the compiler can provide assurance that a certain code pattern provides void-safe protection, then the developer has that pattern available as a CAP. Likewise, even if a pattern can be shown to be a CAP, but for some reason it is not supported by the compiler, then that pattern is not available as a CAP and the compiler will not allow its use. If the compiler can provide assurance that a certain code pattern guarantees void-safe protection, then the developer will have that pattern available as a CAP. Likewise, even if a pattern can be shown logically to be a CAP, but for some reason it is not supported by the compiler, then that pattern will not available as a CAP and the compiler will not allow its use.