... (_URB_CONTROL_TRANSFER(_EX)) down the stack. d -- Please do not send e-mail directly to this alias. this alias is for newsgroup purposes only. This posting is ... WRITE functionality (like beep buzzer, blink error LED) Is it possible for the functional driver to directly access usb endpoint 0? I could not find any DDK calls that can allow this access. Thanks

We plan to use endpoint 0 (control type) for some function specific WRITE functionality (like beep buzzer, blink error LED) Is it possible for the functional driver to directly access usb endpoint 0? I could not find any DDK calls that can allow this access. Thanks

...advantages of UTF-8 are its compactness for the current UCS character sets, compatibility with ASCII files, independence of byte-ordering (lost for direct access) and ability to handle the full set of UCS characters. UTF-16 has not been widely accepted outside of Java, because it ...

glen herrmannsfeldt <gah@ugcs.caltech.edu> wrote: With fixed length records (usual for direct access) and variable length data you need some way to mark the end of the actual data. One way is with a length, the other is with some type of mark. With UTF-8 and variable length codes the length gets even more interesting....

...> it certainly. It was just easier with the implementation built to be orthogonal with respect to issues like that. With fixed length records (usual for direct access) and variable length data you need some way to mark the end of the actual data. One way is with a length, the other is with ...

...main advantages of UTF-8 are its compactness for the current UCS character sets, compatibility with ASCII files, independence of byte-ordering (lost for direct access) and ability to handle the full set of UCS characters. UTF-16 has not been widely accepted outside of Java, because it is...

... in the combination of UTF-8 and direct I/O that actually undoable. And encouraging ... not want to use UTF-8 for direct I/O anyway. It won't be any... the standard that prohibits implementing UTF-8 direct I/O files as UTF-32 internally.... sets, compatibility with ASCII files, independence of byte-ordering (lost for direct access) and ability to handle the full set of UCS characters. UTF-16...

... the line break of the sytsem trying to read the file. This would refer to sequential formatted, not direct access formatted (where you don't need record markers, it is encoded in the length). Then the main ... a normal editor. This will be worse than for an ASCII formatted direct file as bytes in the record lengths will sometimes be interpreted as the...

... to read the file. This would refer to sequential formatted, not direct access formatted (where you don't ... It is not prohibited for direct I/O records to be terminated ... users to decide whether they wanted direct I/O files to have record ... If you wrote a file with direct I/O *and* record marks, you... you could subsequently read it with direct I/O. This was handy to ...

... break of the sytsem trying to read the file. This would refer to sequential formatted, not direct access formatted (where you don't need record markers, it is encoded in the length). The ... does need to know where the end it. (*) For OS/360 (and through z/OS) direct access files are stored with one physical disk block per record. (Though now most disks ...