Results 141 to 150 of about 1,723 (188)
Some of the next articles are maybe not open access.
IBM Systems Journal, 2004
We propose a name service that enables construction of a uniform, global, hierarchical namespace, a key feature needed to create a file-system grid. Combined with other grid replication and location-lookup mechanisms, it supports independence of position for users and applications as well as transparency of data location in a scalable and secure ...
O. Ted Anderson +5 more
openaire +1 more source
We propose a name service that enables construction of a uniform, global, hierarchical namespace, a key feature needed to create a file-system grid. Combined with other grid replication and location-lookup mechanisms, it supports independence of position for users and applications as well as transparency of data location in a scalable and secure ...
O. Ted Anderson +5 more
openaire +1 more source
, 2005 2017
EOS is the distributed storage system being developed at CERN with the aim of fulfilling a wide range of data storage needs, ranging from physics data to user home directories. Being in production since 2011, EOS currently manages around 224 petabytes of disk space and 1.4 billion files across several instances.
Andreas J. Peters +2 more
openaire +1 more source
EOS is the distributed storage system being developed at CERN with the aim of fulfilling a wide range of data storage needs, ranging from physics data to user home directories. Being in production since 2011, EOS currently manages around 224 petabytes of disk space and 1.4 billion files across several instances.
Andreas J. Peters +2 more
openaire +1 more source
2020
While cramming all your code into a single source file is always possible (even for huge programs), a larger code base is far easier to manage if you organize related source code (functions, constants, types, and so on) into logical, composable units, each in their own files.
Ivor Horton, Peter Van Weert
openaire +1 more source
While cramming all your code into a single source file is always possible (even for huge programs), a larger code base is far easier to manage if you organize related source code (functions, constants, types, and so on) into logical, composable units, each in their own files.
Ivor Horton, Peter Van Weert
openaire +1 more source
2001
C++ supports modular programming through a mechanism called namespace. A namespace is a logical unit that contains related declarations and definitions. The idea of modular programming is to divide a large program into small and logically related parts for easy management and information hiding. Dividing a large program into different parts and storing
openaire +1 more source
C++ supports modular programming through a mechanism called namespace. A namespace is a logical unit that contains related declarations and definitions. The idea of modular programming is to divide a large program into small and logically related parts for easy management and information hiding. Dividing a large program into different parts and storing
openaire +1 more source
2010
Namespaces are the means by which you divide your Clojure code into logical groups, similar to packages in Java or modules in other languages. Almost every Clojure source file begins with a namespace declaration using the ns macro. The following code is an example of a namespace declaration: $$ \begin{gathered} \left( {ns clojure.contrib.gen - html
Luke VanderHart, Stuart Sierra
openaire +1 more source
Namespaces are the means by which you divide your Clojure code into logical groups, similar to packages in Java or modules in other languages. Almost every Clojure source file begins with a namespace declaration using the ns macro. The following code is an example of a namespace declaration: $$ \begin{gathered} \left( {ns clojure.contrib.gen - html
Luke VanderHart, Stuart Sierra
openaire +1 more source
2003
Since the creation of the Internet Corporation for Assigned Names and Numbers (ICANN), the regulation of the Domain Name System (DNS) has become a central topic in Internet law and policy discussions. ICANN's critics argue that ICANN uses its technical control over the DNS as undue leverage for policy and legal control over the DNS itself and over ...
openaire +1 more source
Since the creation of the Internet Corporation for Assigned Names and Numbers (ICANN), the regulation of the Domain Name System (DNS) has become a central topic in Internet law and policy discussions. ICANN's critics argue that ICANN uses its technical control over the DNS as undue leverage for policy and legal control over the DNS itself and over ...
openaire +1 more source
2013
Nearly every name in the standard library begins with std::, and only names in the standard library are permitted to start with std::. For your own names, you can define other prefixes, which is a good idea and an excellent way to avoid name collisions. Libraries and large programs in particular benefit from proper partitioning and naming.
openaire +1 more source
Nearly every name in the standard library begins with std::, and only names in the standard library are permitted to start with std::. For your own names, you can define other prefixes, which is a good idea and an excellent way to avoid name collisions. Libraries and large programs in particular benefit from proper partitioning and naming.
openaire +1 more source
2020
Novice Perl programmers typically are told that Perl has no scope by default. While not technically accurate, without packages, variables in Perl appear to be global.
openaire +1 more source
Novice Perl programmers typically are told that Perl has no scope by default. While not technically accurate, without packages, variables in Perl appear to be global.
openaire +1 more source
2002
This chapter introduces you to the .NET way of doing things and explains all the classes, interfaces, and important methods involved in localizing a .NET application using the System.Globalization namespace. There is quite a lot to learn in this chapter. The globalization features of .NET are very comprehensive indeed.
openaire +1 more source
This chapter introduces you to the .NET way of doing things and explains all the classes, interfaces, and important methods involved in localizing a .NET application using the System.Globalization namespace. There is quite a lot to learn in this chapter. The globalization features of .NET are very comprehensive indeed.
openaire +1 more source