InvalidBase64Data class: Difference between revisions
Jump to navigation
Jump to search
m (1 revision) |
m (tags and links) |
||
| Line 1: | Line 1: | ||
<!-- InvalidBase64Data class --> | <!-- InvalidBase64Data class --> | ||
The InvalidBase64Data exception class describes an exception associated with | The <var>InvalidBase64Data</var> exception class describes an exception associated with finding non-base64-encoded data where base64-encoded data was expected, usually when decoding base64-encoded data. | ||
finding non-base64-encoded data where base64-encoded data was expected, | |||
usually when decoding base64-encoded data. | |||
To produce an InvalidBase64Data exception, you typically use a User Language | To produce an <var>InvalidBase64Data</var> exception, you typically use a User Language <var>[[Throw]]</var> statement with an <var>InvalidBase64Data</var> <var>[[New_(InvalidBase64Data_constructor)|New]]</var> constructor. This statement must be issued from within a method, and it can only be caught by the code that calls the method. For example, the following statement throws an <var>InvalidBase64Data</var> exception with the position set to <code>2</code>: | ||
Throw statement with an InvalidBase64Data New constructor. | <p class="code">throw %(invalidBase64Data):new(position=2) | ||
This statement must be issued from | |||
within a method, and it can only be caught by the code that calls the method. | |||
For example, | |||
the following statement throws an InvalidBase64Data exception with the | |||
position set to <code>2</code>: | |||
<p class="code"> throw %(invalidBase64Data):new(position=2) | |||
</p> | </p> | ||
The methods in this class are listed at "[[List of InvalidBase64Data | The methods in this class are listed at "[[List_of_InvalidBase64Data_methods|List of InvalidBase64Data methods]]". | ||
methods]]". | |||
[[Category:System exception classes]] | [[Category:System exception classes]] | ||
Revision as of 05:11, 22 April 2011
The InvalidBase64Data exception class describes an exception associated with finding non-base64-encoded data where base64-encoded data was expected, usually when decoding base64-encoded data.
To produce an InvalidBase64Data exception, you typically use a User Language Throw statement with an InvalidBase64Data New constructor. This statement must be issued from within a method, and it can only be caught by the code that calls the method. For example, the following statement throws an InvalidBase64Data exception with the position set to 2:
throw %(invalidBase64Data):new(position=2)
The methods in this class are listed at "List of InvalidBase64Data methods".