Results for: "remove_const"

Does not print anything when complete as this object has taken a vow of silence.

Prints out the terminal message.

Prints out the terminal message.

The silent download reporter won’t tell you when the download is done. Because it is silent.

Indicates the download is complete.

Returns the same as calling inspect on the string representation of to_str

Compile a InstanceVariableAndWriteNode node

Compile a InstanceVariableOperatorWriteNode node

Compile a InstanceVariableOrWriteNode node

@foo &&= bar

becomes

@foo && @foo = bar

@foo ||= bar

becomes

@foo || @foo = bar

@foo += bar

becomes

@foo = @foo + bar

Dispatch enter and leave events for InstanceVariableAndWriteNode nodes and continue walking the tree.

Dispatch enter and leave events for InstanceVariableOperatorWriteNode nodes and continue walking the tree.

Dispatch enter and leave events for InstanceVariableOrWriteNode nodes and continue walking the tree.

Copy a InstanceVariableAndWriteNode node

Copy a InstanceVariableOperatorWriteNode node

Copy a InstanceVariableOrWriteNode node

Serializes the DH parameters to a PEM-encoding.

Note that any existing per-session public/private keys will not get encoded, just the Diffie-Hellman parameters will be encoded.

PEM-encoded parameters will look like:

-----BEGIN DH PARAMETERS-----
[...]
-----END DH PARAMETERS-----

See also public_to_pem (X.509 SubjectPublicKeyInfo) and private_to_pem (PKCS #8 PrivateKeyInfo or EncryptedPrivateKeyInfo) for serialization with the private or public key components.

Serializes a private or public key to a PEM-encoding.

When the key contains public components only

Serializes it into an X.509 SubjectPublicKeyInfo. The parameters cipher and password are ignored.

A PEM-encoded key will look like:

-----BEGIN PUBLIC KEY-----
[...]
-----END PUBLIC KEY-----

Consider using public_to_pem instead. This serializes the key into an X.509 SubjectPublicKeyInfo regardless of whether it is a public key or a private key.

When the key contains private components, and no parameters are given

Serializes it into a traditional OpenSSL DSAPrivateKey.

A PEM-encoded key will look like:

-----BEGIN DSA PRIVATE KEY-----
[...]
-----END DSA PRIVATE KEY-----

When the key contains private components, and cipher and password are given

Serializes it into a traditional OpenSSL DSAPrivateKey and encrypts it in OpenSSL’s traditional PEM encryption format. cipher must be a cipher name understood by OpenSSL::Cipher.new or an instance of OpenSSL::Cipher.

An encrypted PEM-encoded key will look like:

-----BEGIN DSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,733F5302505B34701FC41F5C0746E4C0

[...]
-----END DSA PRIVATE KEY-----

Note that this format uses MD5 to derive the encryption key, and hence will not be available on FIPS-compliant systems.

This method is kept for compatibility. This should only be used when the traditional, non-standard OpenSSL format is required.

Consider using public_to_pem (X.509 SubjectPublicKeyInfo) or private_to_pem (PKCS #8 PrivateKeyInfo or EncryptedPrivateKeyInfo) instead.

Obtains a list of all predefined curves by the OpenSSL. Curve names are returned as sn.

See the OpenSSL documentation for EC_get_builtin_curves().