Samond Classes Library 1.2.6-STABLE build 219
Library error messages

Table of Contents

Library errors

During the library code execution can result in various run-time error, processing of which depends on the module in which the error occurred. Some modules can provide error-handling mode selection, the other modules always generate exceptions.

Read more about the mechanism of errors processing described in the section Programming Guide Exceptions Programmer's Guide.


Common library errors

These errors are not specific to the module, and to the entire library at once.

SCL-20000: generic unspecified error

Exception SCException is a common ancestor of all the other exceptions. It defines the concept of generic undefined error, but no one module does not generate this error. This error was introduced solely for the structuring of the error messages.

SCL-20001: abstract method calling

The error occurs when you attempt to call an abstract method of a class, for example, in such a situation, how to work with an abstract class instead of the appropriate child class. At detection of this error is generated exception SCAbstractMethodException.

This error is generated by the following library classes:

SCL-20002: system error

It may occur when a system call or a standard C/C++/Objective-C library returns an error message. When this error detects, exception SCSystemException generates.

Generates the following classes and categories:


NSNumber errors

These errors may occur when operating with numerical objects based on a standard class NSNumber and expanding its category NSNumber(SCNumber). At detection of this error is generated exception SCNumberException.

SCL-20010: unspecified NSNumber error

Abstract error that can theoretically be occur when operating with numeric objects. Currently, the program code of the library does not generate this error.

SCL-20011: unsupported number object type

The error occurs in cases when streams and collections modules detect an unknown type of numeric object. This can happen when Apple has made changes to the NSNumber class, and we did not have time to make changes to our code.


Stream errors

These errors are detected by the stream unit. If you do not use special stream error handlers, stream status changes or a system error generation (class SCSystemException), the exception SCStreamException is generated.

SCL-20020: unspecified stream error

This error is using for describing the unspecified stream error. Library code do not generate this error.

SCL-20021: stream not open

The error occurs when attempting to perform read and write operations with the stream, which was not open.
When the stream module detects this error, it generates the exception SCStreamException.
Name of erroneous stream You can read from property SCStreamException::streamName.

This error can be detected during calling the following classes:

SCL-20022: read only stream

This error occurs when streams unit detects the attempt to write data into read only stream.
If the streams unit detects this error, it generates the exception SCStreamException.
Name of erroneous stream You can get from the property SCStreamException::streamName.

Error SCL-20022 can be occured by using the following classes:

SCL-20023: write only stream

This error occurs when streams unit detects the attempt to read data from write only stream.
When the streams unit detects this error, it throw the exception SCStreamException.
Property SCStreamException::streamName contains the erroneous stream name.

This error can be detected during using the following classes:

SCL-20024: unknown class

When the stream detects object of the unknown class during read operations, the stream unit detects the error SCL-20024 and generates the exception SCStreamException. This error occurs when the code attemps read data from stream created by using the different version of the software.

Error information can be obtain from the following SCStreamException properties:

Error can be detected during using the following classes:

SCL-20025: unexpected class

This error occurs when the stream detects the object of one class instead the object of the required classs. Typically it occurs when a program attempts to read from the stream did not an instance of the class that it contains. For example, in a stream are NSString instance of class, while the program tries to read the data of instance NSNumber class. During processing this error stream unit cat generate the exception SCStreamException.

Information about this error can be readed from the following properties of the class SCStreamException:

This error can be detected by using the following classes:

SCL-20026: unsupported class

If the stream detects the class, which do not support the SCStreaming protocol, occurs error SCL-20026 and generates the exception SCStreamException.

Error information contains in the following properties of the class SCStreamException:

Error SCL-20026 can be occured in the following classes:

SCL-20027: incompleted read operation

Error occurs when the stream reads less characters than expected.
At detection this error streams unit can generate the exception SCStreamException.

Related error data can be read from the following class SCStreamException properties:

Error can be generated by using the following classes:

SCL-20028: incompleted write operation

Error occurs when the stream writes less characters than expected.
At detection this error streams unit can generate the exception SCStreamException.

Information about detected SCL-20028 error contain in the following class SCStreamException properties:

Error can be detected in the following classes:

SCL-20029: stream opening error

Error occurs during stream opening attempt. This most often happens when attempting:

During this error processing can be generated exception SCStreamException.

The following properties of the class SCStreamException contain error information:

Error occurs during using the following classes:

SCL-20030: data read error

Error occurs during read operation from the stream and usually associated with any system problems or problems with the media.
Exception SCStreamException may be generated if the error SCL-20030 detected.

Error information can be getting from the following class SCStreamException properties:

This error can be generated by using the following classes:

SCL-20031: data write error

Error occurs during write operation from the stream and usually associated with any system problems or problems with the media.
Exception SCStreamException may be generated if the error SCL-20031 detected.

Error information can be getting from the following class SCStreamException properties:

This error can be generated by using the following classes:

SCL-20032: NSNumber error

Error occurs during reading or writing NSNumber instance. It corresponds with error SCL-20011.
If stream unit detects this error, can be generated the exception SCStreamException.

Error data stores in the following properties of the class SCStreamException instance:

Error occurs in the following classes:

SCL-20033: incorrect stream mode

Error occurs when streams unit detects incorrect file stream opening mode, which do not support in the type SCFileStreamOpenMode.
If the streams unit do not processing this error, it generates the exception SCStreamException.

The following class SCStreamException properties contain information abot detected error:

SCL-20034: empty file stream path

Error occurs when the file stream detects the empty path to file.
Stream unit can generate the exception SCStreamException.

SCL-20035: end of stream

When the class SCFileStream instance attempts read data outside the stream, streams unit can generate the exception SCStreamException.
Path to erroneous file stream You can read from the property streamName.

SCL-20036: incorrect offset

If the positioning methods of the class SCFileStream detect the incorrect stream offset, the streams unit fixes the error SCL-20036 and can generate the exception SCStreamException.

The following properties of the class SCStreamException instance store the information about this error:

SCL-20037: incorrect offset whence

Error occurs when the stream detects the incorrect offset whence.
Streams unit can throw the exception SCStreamException.

For getting access to error data You can use values from the following class SCStreamException properties:


Collection errors

Described in this section, errors may occur during the using the various collections.
Depending on the collection failure processing mode, collections unit can throw the exception SCCollectionException.

SCL-20040: unspecified collection error

Error SCL-20040 is an abstract collection error. Library source code do not throw this exception, but You can use this error for custom collection exception throwing.

SCL-20041: source collection does not exist

The rrror occurs when you try to create or initialize a new collection based on an existing collection, or when you try to copy data from the another collection. There is an error in this case, if the original collection does not exist - cause an error method passes a null pointer.

An error may occur when operation the following classes:

SCL-20042: unsupported collection type

This error is largely similar to the previously described error SCL-20041, but there is in the case of getting as argument of relevant method an instance of non-collection class (class, which do not support the protocol SCCollection). An example of this is the use, instead of a pointer to an SCCollection class instance pointer to an instance of the class NSString.

The name of the unsupported class can be found via the property typeName of the class SCCollectionException class instance.

Error may occur when using the instances of the following classes:

SCL-20043: collection is read-only

The error occurs when trying to make changes in the collection, which is in read-only mode. The name of the collection caused the error can be obtained through the property collectionName of the exception class SCCollectionException.

Error may be detected when using the following classes:

SCL-20044: adding a null pointer

It occurs when you try to add to the collection a null pointer to the class instance.
The name of the collection caused the error can be obtained through the property collectionName of class SCCollectionException.

Error may occur when using with the following classes:

SCL-20045: source object does not exist

The error occurs when attempting to create or initialize a new collection based on an existing object.
Unlike the error SCL-20041 is that this error does not occur when you create a collection based on another collection, and during the creation of the collection of a single specified source object.
This error occurs in case the source object does not exist - cause an error method passes a null pointer.

Error can occur when operating with the following classes:

SCL-20046: unsupported class

The error occurs when the collection encounters instance of the class that has no methods of interaction with the collections unit, that is, does not correspond SCCollectioning protocol.
The name of an unsupported class, you can get through property unsupported of exception class SCCollectionException.

Error can occur when using with the following classes:

SCL-20047: unknown class

The error occurs when the collections unit encounters the class, are unknown to the system, so it is impossible to create an instance of class. The main cause of this error is a mismatch software versions, such as the program attempts to load data created with a newer version.
Name of the unknown class can be accessed through the property unknown of the exception class SCCollectionException.

Error can be detected during using the instances of the following classes:

SCL-20048: incomparable collection object

It occurs when you try to collections unit carry out the comparison of objects that can not be compared with each other.

This error occurs by using the following classes:

SCL-20049: collection does not support sorting

The error is caused when trying to to sort a collection that does not support this capability, for example, you can not sort the data sets or dictionaries.

Error can occur during operation with the following classes:

SCL-20050: incorrect data sorter

The error occurs during the sorting data in the collection, if the collections unit detects that it is a pointer to nonexistent sorter or a pointer to an instance that is not a data sorter (does not match protocol SCSorter).

Error may occur when using with the following classes:

SCL-20052: incorrect index

This error occurs when you try to access an array element with index inappropriate, for example, the event that index of the requested object is outside of the array. Incorrect index can be obtain from the class SCCollectionException property index.

Error can be detected during using the instances of the following classes:

SCL-20053: incorrect objects range

This error occurs when trying to access the elements of an array with a range of inappropriate objects. Cause an error range of objects can be found via the property range of the class SCCollectionException.

Error may occur when using with the following classes:

SCL-20054: incorrect index set

The error occurs in one of the following cases:

Obtain information on the index set possible through the property indexSet of class SCCollectionException instance.

Error may occur when using with the following classes:

SCL-20055: number of indexes does not match number of objects

The error occurs when some methods of collections unit receive as arguments the index set and objects list that have a different elements number.

The error information is contained in one of the properties of the class SCCollectionException:

An error may occur when working with the following classes:

SCL-20056: incorrect object key

It occurs when you try to send a non-existent dictionary key or to request data record with a missing key in the dictionary. Data on the cause errors key can be obtained from the property key of class SCCollectionException instance.

Error may occur when using the following classes:

SCL-20057: number of keys does not match number of objects

The error occurs when some methods of collections unit receive as arguments the keys list and objects list that have a different elements number.

The error information is contained in one of the properties of the class SCCollectionException:

An error may occur when working with the following classes:

SCL-20058: empty value

It occurs when you try to set for any key of the dictionary the empty value. The key name can determine through the property key of the class SCCollectionException.

Error may occur during operation with the following classes:


Text errors

Described in this section, the errors may occur during operation with different classes of text. At detection of these errors text classes can generate an exception SCTextException.

SCL-20060: unspecified text error

Text classes abstract error. Library source code do not throw this exception, but You can use this error for custom collection exception throwing.

SCL-20061: source object does not exist

Error occurs when attempting to create the text objects using the non-existent source objects. Also the error can be generated when trying to replace the content of the text object using the contents of a non-existing source object.

This error can be generated during using the following classes:

SCL-20062: incorrect input stream

The error occurs when you attempt to load a text file from the stream. Usually, the cause of this error is either an attempt to reading from a non-existing stream or attempt to read from the stream, which available only for writing operations. Information about incorrect stream is available through class SCTextException stream property.

Error may occur when using with the class SCTextFile.

SCL-20063: text is read only

Error occurs when you try to make changes to the text that is in read-only mode. Name of erroneous text can be found in the class SCTextException instance textName property.

Error may occur when using with the following classes:

SCL-20064: null string adding

Error occurs when attempting to add into the text a null string (null pointer class instance). Null string can not be confused with an empty string, which is a real class NSString instance, but not contains any characters. The name of erroneous text contains in the property textName of class SCTextException instance.

Error may be generated inside of one of the following classes:

SCL-20065: closed stream

The error occurs when trying to read or write the text from the stream that has not been previously opened. Information about incorrect stream can be obtained from the property stream of the class SCTextException instance.

Error may occur when using the class SCTextFile.

SCL-20066: not string instance

Error occurs when the text object attempts processing item, which does not instance of the class NSString or child class of NSString. Name of this erroneous class can be obtained from the class SCTextException property unsupported.

Error may generate when using the instances of the following classes:

SCL-20067: reading error

The exception is generated when an error occurs during the reading text information from the stream. Erroneous stream information can be obtained from the class SCTextException instance property stream.

Error may occur in the class SCTextFile.

SCL-20068: empty text file path

The error occurs when trying to read or write a text file with an empty path. SCTextFile may occur in grade.
An error may occur in SCTextFile class.

SCL-20069: string unique violation

Error occurs when attempring to add into the unique strings list (class SCUniqueStrings instance) the string that already exists in this list. Generation of this error is also possible when trying to change the string, if the new line is already in the list with a different string index.

The error information is contained in the following class SCTextException instance properties:

Error may occur when using the class SCUniqueStrings.

SCL-20070: incorrect strings sorter

The error occurs during the string sorting in the text if the text unit detects that it receives null pointer to the strings sorter or pointer is not SCSorter protocol instance.

Error may occur during working with instances of the following classes:

SCL-20071: incorrect output stream

Error occurs when attempt to save the text into the stream. Usually, the cause of this error is either an attempt to write to non-existent output stream or attempt to write to the read-only stream. Information about incorrect output stream is available through property stream of class SCTextException instance.

Error may occur when using the class SCTextFile instances.

SCL-20072: incorrect string index

The error occurs when trying to access the index, exceed a text. For more information about the error can be found out through the the following properties of class SCTextException instance:

Error may be generated by the following classes:

SCL-20073: incorrect string range

This error occurs when attemting to getting the text in the incorrect range. Erroneous string range cat be obtained from the class SCTextException instance property range.

Error may be detected during working with the following classes:

SCL-20074: incorrect index set

The error occurs in one of the following cases:

Obtain information about incorrect index set can be getting through the indexSet property of class SCTextException instance.   Error may occur when using the following classes:

SCL-20075: number of indexes does not match number of strings

This error is generated by some methods of the text objects when it detects a mismatch between the number of strings and number of indexes. Information about this error can be obtained through the following properties of class SCTextException instance:

Error can be generated by the instances of the following classes:

SCL-20076: intersected string ranges

The error occurs when trying to process strings in overlapping ranges, whereas the logic requires that ranges were independent from each other, for example, in operations of exchange strings between two ranges. Advanced information about this error can be obtained from the following properties of class SCTextException instance:

This error can be detected in the instances of the following classes:

SCL-20077: writing error

The error is generated when a failure occurs during writing text into the stream. Information about erroneous stream can be obtained from the class SCTextException instance property stream.

Error may be generated during working with the class SCTextFile.


Runtime errors

SCL-20080: unspecified runtime error

SCL-20081: class runtime error

SCL-20082: selector runtime error

SCL-20083: method implementation runtime error

SCL-20084: type runtime error

SCL-20085: property runtime error

SCL-20086: protocol runtime error

SCL-20087: instance variable runtime error

SCL-20088: method runtime error