|
| |
| | Citations: There is a silver bullet - Cox (ResearchIndex) |
 | | Claims made about the advantages of the object oriented paradigm are based primarily on opinions or anecdotes rather than on rigorous and quantitative studies and metrics to support the claims [9, 17] Software metrics have been proposed for both the procedural and the object oriented paradigms.... | | | The look and behavior of agents is controlled by designers using Agentsheets to create dynamic visual environments with domain oriented spatio temporal metaphors. | | | Such advantages are presented as corollaries of the intensive use of the data encapsulation and reuse facilities made available by the object oriented development languages and systems [DMN67, GR83, Str86, Cox86, Mey88] Object orientation seems also to pay off at the level of software.... |
|
http://citeseer.ist.psu.edu/context/22035/0
|
|
| |
| | Byte Code Engineering with the JavaClass API - Dahm (ResearchIndex) |
| | Since Java classes are compiled into portable binary class files (called byte code), it is the most convenient and platform-independent way to... | | | Abstract: Extensions and improvements of the programming language Java and its related execution environment (Java Virtual Machine, JVM) are the subject of a large number of research projects and proposals. | | | There are projects, for instance, to add parameterized types to Java, to implement "Aspect-Oriented Programming", and to improve the run-time performance. |
|
http://citeseer.ist.psu.edu/dahm99byte.html
|
|
| |
| | Creating a ''One to One" Adaptive Huffman Compression/Decompression Program for the real world of 8 bit byte files |
| | Since the decompression routine is always looking at 8-bit byte input files and the Huffman decompression scheme will seldom end on the filling of the last byte, here is where one must look. | | | The problem now is how to add the information of a new symbol into the table, and how to end the file in a reasonable way if the file does not end in a complete last byte. | | | Fact three: A one byte Huffman file has no hidden bits and decompresses to one byte since the start tree has 256 leaves, all at a length of 8 bits. |
|
http://bijective.dogma.net/dspaper.htm
|
|
| |
| | Implementation Types |
| | The iterative for statement, the associated find guarded conditional statements and the for_all and exists quantifiers incorporating a byte prefixed for list may be set up to iterate on values of the byte type spaced in wrap-around byte arithmetic progression. | | | A byte notation is valid only if the included based integer is able to yield a valid byte; no modulo operation is performed if it is not the case. | | | The iterative traversal statement, the associated search guarded conditional statements and the all_of and one_of quantifiers incorporating a byte prefixed through list may be set up to iterate on the constituant bits of a given byte value. |
|
http://diwww.epfl.ch/w3lco/pub/Newton/implementation_types.html
|
|
| |
| | Using Pattern Languages for Object-Oriented Programs |
| | For example, external files can have complex or highly encoded formats that require substantial byte or even bit manipulation to interpret. | | | Often many objects need to communicate with low-level (bit- or byte-oriented) parts of the system. | | | Collect all necessary protocol for decoding file formats or any other particular low-level task into an object specifically designed for the purpose. |
|
http://c2.com/doc/oopsla87.html
|
|
| |
| | ShiftJIS::Regexp - Shift_JIS-oriented regular expressions on byte-oriented perl |
| | In character classes, any character or byte sequence that does not match any one Shift_JIS character, e.g. | | | is not prevented from matching trail byte of the previous double byte character: e.g. | | | , to avoid mismatching a single-byte character on a trailing byte of a double-byte character, or a double-byte character on two bytes before and after a character boundary. |
|
http://cpan.uwinnipeg.ca/htdocs/ShiftJIS-Regexp/ShiftJIS/Regexp.html
|
|
| |
| | SHS Validation List |
| | In cases where the implementation was tested and is validated only for the correct generation of a message digest on byte -oriented data, this is indicated by " (BYTE-only) " in the description field. | | | The SHA-1 implementation does not process message lengths > 1500 bytes. | | | However, if " (BIT) " is indicated, then the implementation is validated as conforming to the standard for bit-oriented messages (i.e., where the message length does not have to be a multiple of 8 bits). |
|
http://csrc.nist.gov/cryptval/shs/shaval.htm
|
|
|
