to allow you to nest command line utilities. The idea is that you can have a system that works together with another system by tacking two Click instances together and they will continue working as they Python library that aims to create a level of composability of applications that goes beyond what the system itself supports. Docopt, for instance, acts by parsing your help pages and then parsing according tradeoffs that need to be made and in case of argparse these tradeoffs have been critical enough, that a system like Click cannot even be implemented on top of it. In this particular case, Click attempts to stay

...................................................................... 17 L'instruction CREATE DATABASE ............................................................................................. 17 utiliser les an- ciennes applications) \bin (avec en option une copie dans Windows System – voir la note en bas de ta- bleau) Répertoire d'installation (désigné ensuite comme ) Windows System dépend de votre version de Windows. Habituellement on a: • pour Windows 95/98/ME: C:\Windows\System • pour Windows NT/2000: C:\WINNT\System32 • pour Windows XP: C:\Windows\System32 Installer

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.4) 1 / 167 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.1) 1 / 146 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.3) 1 / 159 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.2) 1 / 159 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.6) 1 / 173 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

un participant : • actor • boundary • control • entity • database @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 -> Foo3 Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections @enduml Guide de référence du langage PlantUML (1.2019.9) 1 / 173 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d'utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User

For example, on HP-UX 10.20 or 11.00 Unix systems, the maximum file size is 2 Gb unless the file system has the largefiles option turned on. This limit still exists on some operating systems. Gsplit from the gbak utility (when backing up a database) to be split into a number of chunks, or a number of chunks to be joined together and used to restore a database. Up until Interbase 5.0, dump files were were limited to 2 Gb by the gbak utility itself — even if running on a system which allowed files to be 4 Gb. Coming up in the remainder of this manual, we will discuss the following: • Command line options

participant : • actor • boundary • control • entity • database • collections @startuml actor Foo1 boundary Foo2 control Foo3 entity Foo4 database Foo5 collections Foo6 Foo1 -> Foo2 : To boundary Foo1 Foo1 -> Foo3 : To control Foo1 -> Foo4 : To entity Foo1 -> Foo5 : To database Foo1 -> Foo6 : To collections Guide de référence du langage PlantUML (1.2021.2) 1 / 390 1.2 Déclaration de participants 1 DIAGRAMME définition des acteurs et des cas d’utilisation avec << et >>. @startuml User << Human >> :Main Database: as MySql << Application >> (Start) << One Shot >> (Use the application) as (Use) << Main >> User