Форум программистов «Весельчак У»
  *
Добро пожаловать, Гость. Пожалуйста, войдите или зарегистрируйтесь.
Вам не пришло письмо с кодом активации?

  • Рекомендуем проверить настройки временной зоны в вашем профиле (страница "Внешний вид форума", пункт "Часовой пояс:").
  • У нас больше нет рассылок. Если вам приходят письма от наших бывших рассылок mail.ru и subscribe.ru, то знайте, что это не мы рассылаем.
   Начало  
Наши сайты
Помощь Поиск Календарь Почта Войти Регистрация  
 
Страниц: [1] 2  Все   Вниз
  Печать  
Автор Тема: [C++ Error] E2277 Lvalue required  (Прочитано 53651 раз)
0 Пользователей и 1 Гость смотрят эту тему.
MOPO3
Ай да дэдушка! Вах...
Команда клуба

lt
Offline Offline
Пол: Мужской
Холадна аднака!


WWW
« : 21-07-2004 06:23 » 

Есть код в примере :
Код:
void __fastcall TForm1::TriggerAvail(TObject *CP, WORD Count)
{
    WORD I; char C; String Buffer[255]; int BufferIndex;
    for(I = 1; I <= Count; I++)
    {
       C = ApdComPort1->GetChar();
       Buffer = Buffer + C; //здесь ошибка
       AdTerminal1->WriteString("Got Hello!");
    }
}

при компиляции выдаёт ошибку(САБЖ). Что и как нужно сконвертить чтобы нормально сработало ?
« Последнее редактирование: 30-11-2007 20:51 от Алексей1153++ » Записан

MCP, MCAD, MCTS:Win, MCTS:Web
PSD
Главный специалист

ru
Offline Offline
Пол: Мужской

« Ответ #1 : 21-07-2004 06:38 » 

А разве брланд позволяет так работать со строками ?

В MFC  есть похожий класс СString вот у него орератор плюс перегружен только для типа СString  те

СString a,b;
char s ="dddd";
a=s; // можно
a=a+b //можно
a=a+s //нельзя,  нужно  a=a+CString (s)

В данном конкретном случае смею предположить что оператор +  не переопределен для типа char, проверь по докам.
Записан

Да да нет нет все остальное от лукавого.
ixania
Гость
« Ответ #2 : 21-07-2004 10:21 » 


Из примера видно что автор понятия не имеет что ето за обьект String, если посмотреть в sysmac.h где String обьявлен то увидите следующее

typedef AnsiString String;  8)

насколько я понял суть кода, то он должен выглядеть следующим образом:


1.----------------------------------------------------------------------------
void __fastcall TForm1::TriggerAvail(TObject *CP, WORD Count)
{
   String Buffer;

    for(WORD I = 0; I < Count; I++)
    {

       Buffer += ApdComPort1->GetChar();

       AdTerminal1->WriteString("Got Hello!");
    }
}
------------------------------------------------------------------

2.---------------------------------------------------------------
void __fastcall TForm1::TriggerAvail(TObject *CP, WORD Count)
{
   char* Buffer = new char[Count];

    for(WORD I = 0; I < Count; I++)
    {

       Buffer[I] = ApdComPort1->GetChar();

       AdTerminal1->WriteString("Got Hello!");
    }

    delete Buffer;
}
« Последнее редактирование: 21-04-2006 22:17 от Алексей1153 » Записан
Anchorite
Гость
« Ответ #3 : 22-07-2004 15:18 » 

Ну вы блин даете - Buffer являктся ИМЕНЕМ МАССИВА, а следовательно КОНСТАНТНЫМ ВЫРАЖЕНИЕМ. Константы не являются леводопустимыми выражениями, т.к. им ничего нельзя присвоить.  Вот и получается -  [C++ Error] E2277 Lvalue required.
Записан
MOPO3
Ай да дэдушка! Вах...
Команда клуба

lt
Offline Offline
Пол: Мужской
Холадна аднака!


WWW
« Ответ #4 : 23-07-2004 04:40 » 

Да понял, понял я уже ! Хватит каинями то бросаться Жаль  Всю охоту задавать вопросы отбиваете Жаль Я на билдере и цпп пишу то всего три месяца...
Записан

MCP, MCAD, MCTS:Win, MCTS:Web
reconnector
Гость
« Ответ #5 : 03-04-2005 11:05 » 

Господа может и не в тему но помогите чем можите пожалуйста
компиллер C++Builder6.0
какой заголовочный файл надо чтоб вот это заработало Улыбаюсь)))?
Код:
CString str;
           ................................
          ....................................
                .......................
DWORD temp;
  WriteFile(hFile,
            str.GetBuffer(str.GetLength()),
            str.GetLength(),
            &temp,NULL));
   CloseHandle(hFile);   
  ну или каким способом  можно это заменить  ?
                                                                               ЗЫ: Работа идет не с файлом а с псевдофайлом   
« Последнее редактирование: 03-04-2005 11:39 от reconnector » Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #6 : 03-04-2005 12:43 » 

reconnector А VC это вообше работало. По логике вешей str.GetBuffer(str.GetLength()) должно дать ссылку на последний нуль строки. Если я не прав, то я извеняюсь.
Самое простое, что можно получить из этого. И при этом это будет работать и в Билдере и в Вижуале, это
Код:
#include <string.h>
//----------------------------------------------------------------------------------------
char ch[] = "Строка для записи в файл";
DWORD temp=(DWORD) strlen(ch);
WriteFile(hFile, temp, &temp, NULL);
CloseHandle(hFile);
« Последнее редактирование: 03-04-2005 12:46 от Finch » Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #7 : 03-04-2005 14:00 » 

Я вкурсе что в VC это работало я просто пытался на билдер перенести
Нет не работает Это Жаль
Код:
E2034 Cannot convert 'unsigned long' to 'const void *'
 E2342 Type mismatch in parameter 'lpBuffer' (wanted 'const void *', got 'unsigned long')
 E2034 Cannot convert 'unsigned long *' to 'unsigned long'
 E2342 Type mismatch in parameter 'nNumberOfBytesToWrite' (wanted 'unsigned long', got 'unsigned long *')
 E2193 Too few parameters in call to '__stdcall WriteFile(void *,const void *,unsigned long,unsigned long *,_OVERLAPPED *)'
 W8004 'temp' is assigned a value that is never used

а не coздает ли
Цитата
По логике вешей str.GetBuffer(str.GetLength()) должно дать ссылку на последний нуль
буфер размером равным длине строки?
« Последнее редактирование: 30-11-2007 21:01 от Алексей1153++ » Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #8 : 03-04-2005 14:07 » 

А ну правильно, я тут пропустил  заместо WriteFile(hFile, temp, &temp, NULL); надо WriteFile(hFile, ch, temp, &temp, NULL); Сам буфер то в запись то не указал.
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #9 : 03-04-2005 15:31 » 

Все заработало  спасибо Улыбаюсь Тока вот еще один ламерский вопрос Отлично 
как из Edit поместить строку в  char ch[]="";
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #10 : 03-04-2005 15:53 » 

У тебя какой максимальный размер строки будет. И в каком формате она хранится. Потому что  нуль терминальную строку стандартного Edit WinAPI можно напрямую вставлять.
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #11 : 03-04-2005 16:23 » 

Суть такова Пользователем вводится строка в поле  Edit   из Этого поля строка копируется в файл В том виде в каком была введена ... тоесть могут быть введены любые символы
Размер файла не должен привышать 64 кб 
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #12 : 03-04-2005 16:34 » 

Как из Edit ты получаеш строку, в каком формате?
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #13 : 03-04-2005 16:41 » 

если честно то Не знаю Улыбаюсь Я визуал тока начинаю короче получаю строку так :   Form1->Edit1->Text
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #14 : 03-04-2005 18:28 » 

Я создал проект. На форму бросил Edit и кнопку. На кнопке создал событие
Код:
void __fastcall TForm1::Button1Click(TObject *Sender)
{
 HANDLE hFile=CreateFile("MyProb.html",GENERIC_WRITE, 0, NULL,
                          CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL);
 DWORD temp;
 WriteFile(hFile, Edit1->Text.c_str(), Edit1->Text.Length(), &temp, NULL);
 CloseHandle(hFile);
}
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #15 : 03-04-2005 20:32 » 

спасибо помогло Улыбаюсь если бы еще обьяснил как прочитать этот файл ?
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #16 : 04-04-2005 11:58 » 

Заместо WriteFile используй ReadFile
Цитата
The ReadFile function reads data from a file, starting at the position indicated by the file pointer. After the read operation has been completed, the file pointer is adjusted by the number of bytes actually read, unless the file handle is created with the overlapped attribute. If the file handle is created for overlapped input and output (I/O), the application must adjust the position of the file pointer after the read operation.

BOOL ReadFile(

    HANDLE hFile,   // handle of file to read
    LPVOID lpBuffer,   // address of buffer that receives data 
    DWORD nNumberOfBytesToRead,   // number of bytes to read
    LPDWORD lpNumberOfBytesRead,   // address of number of bytes read
    LPOVERLAPPED lpOverlapped    // address of structure for data
   );   
 

Parameters

hFile

Identifies the file to be read. The file handle must have been created with GENERIC_READ access to the file.

Windows NT

For asynchronous read operations, hFile can be any handle opened with the FILE_FLAG_OVERLAPPED flag by the CreateFile function, or a socket handle returned by the socket or accept functions.

Windows 95

For asynchronous read operations, hFile can be a communications resource, mailslot, or named pipe handle opened with the FILE_FLAG_OVERLAPPED flag by CreateFile, or a socket handle returned by the socket or accept functions. Windows 95 does not support asynchronous read operations on disk files.

lpBuffer

Points to the buffer that receives the data read from the file.

nNumberOfBytesToRead

Specifies the number of bytes to be read from the file.

lpNumberOfBytesRead

Points to the number of bytes read. ReadFile sets this value to zero before doing any work or error checking. If this parameter is zero when ReadFile returns TRUE on a named pipe, the other end of the message-mode pipe called the WriteFile function with nNumberOfBytesToWrite set to zero.
If lpOverlapped is NULL, lpNumberOfBytesRead cannot be NULL.
If lpOverlapped is not NULL, lpNumberOfBytesRead can be NULL. If this is an overlapped read operation, you can get the number of bytes read by calling GetOverlappedResult. If hFile is associated with an I/O completion port, you can get the number of bytes read by calling GetQueuedCompletionStatus.

lpOverlapped

Points to an OVERLAPPED structure. This structure is required if hFile was created with FILE_FLAG_OVERLAPPED.

If hFile was opened with FILE_FLAG_OVERLAPPED, the lpOverlapped parameter must not be NULL. It must point to a valid OVERLAPPED structure. If hFile was created with FILE_FLAG_OVERLAPPED and lpOverlapped is NULL, the function can incorrectly report that the read operation is complete.
If hFile was opened with FILE_FLAG_OVERLAPPED and lpOverlapped is not NULL, the read operation starts at the offset specified in the OVERLAPPED structure and ReadFile may return before the read operation has been completed. In this case, ReadFile returns FALSE and the GetLastError function returns ERROR_IO_PENDING. This allows the calling process to continue while the read operation finishes. The event specified in the OVERLAPPED structure is set to the signaled state upon completion of the read operation.

If hFile was not opened with FILE_FLAG_OVERLAPPED and lpOverlapped is NULL, the read operation starts at the current file position and ReadFile does not return until the operation has been completed.
If hFile is not opened with FILE_FLAG_OVERLAPPED and lpOverlapped is not NULL, the read operation starts at the offset specified in the OVERLAPPED structure. ReadFile does not return until the read operation has been completed.

 

Return Values

If the function succeeds, the return value is nonzero.
If the return value is nonzero and the number of bytes read is zero, the file pointer was beyond the current end of the file at the time of the read operation. However, if the file was opened with FILE_FLAG_OVERLAPPED and lpOverlapped is not NULL, the return value is FALSE and GetLastError returns ERROR_HANDLE_EOF when the file pointer goes beyond the current end of file.
If the function fails, the return value is zero. To get extended error information, call GetLastError.

Remarks

ReadFile returns when one of the following is true: a write operation completes on the write end of the pipe, the number of bytes requested has been read, or an error occurs.
If part of the file is locked by another process and the read operation overlaps the locked portion, this function fails.
Applications must not read from nor write to the input buffer that a read operation is using until the read operation completes. A premature access to the input buffer may lead to corruption of the data read into that buffer.

Characters can be read from the console input buffer by using ReadFile with a handle to console input. The console mode determines the exact behavior of the ReadFile function.
If a named pipe is being read in message mode and the next message is longer than the nNumberOfBytesToRead parameter specifies, ReadFile returns FALSE and GetLastError returns ERROR_MORE_DATA. The remainder of the message may be read by a subsequent call to the ReadFile or PeekNamedPipe function.

When reading from a communications device, the behavior of ReadFile is governed by the current communication timeouts as set and retrieved using the SetCommTimeouts and GetCommTimeouts functions. Unpredictable results can occur if you fail to set the timeout values. For more information about communication timeouts, see COMMTIMEOUTS.
If ReadFile attempts to read from a mailslot whose buffer is too small, the function returns FALSE and GetLastError returns ERROR_INSUFFICIENT_BUFFER.

If the anonymous write pipe handle has been closed and ReadFile attempts to read using the corresponding anonymous read pipe handle, the function returns FALSE and GetLastError returns ERROR_BROKEN_PIPE.
The ReadFile function may fail and return ERROR_INVALID_USER_BUFFER or ERROR_NOT_ENOUGH_MEMORY whenever there are too many outstanding asynchronous I/O requests.
The ReadFile code to check for the end-of-file condition (eof) differs for synchronous and asynchronous read operations.

When a synchronous read operation reaches the end of a file, ReadFile returns TRUE and sets *lpNumberOfBytesRead to zero. The following sample code tests for end-of-file for a synchronous read operation:

// attempt a synchronous read operation 
bResult = ReadFile(hFile, &inBuffer, nBytesToRead, &nBytesRead, NULL) ;
// check for eof
if (bResult &&  nBytesRead == 0, ) {
   // we're at the end of the file
   }
 

An asynchronous read operation can encounter the end of a file during the initiating call to ReadFile, or during subsequent asynchronous operation.
If EOF is detected at ReadFile time for an asynchronous read operation, ReadFile returns FALSE and GetLastError returns ERROR_HANDLE_EOF.
If EOF is detected during subsequent asynchronous operation, the call to GetOverlappedResult to obtain the results of that operation returns FALSE and GetLastError returns ERROR_HANDLE_EOF.

To cancel all pending asynchronous I/O operations, use the CancelIO function. This function only cancels operations issued by the calling thread for the specified file handle. I/O operations that are canceled complete with the error ERROR_OPERATION_ABORTED.
The following sample code illustrates testing for end-of-file for an asynchronous read operation:

// set up overlapped structure fields 
// to simplify this sample, we'll eschew an event handle
gOverLapped.Offset     = 0;
gOverLapped.OffsetHigh = 0;
gOverLapped.hEvent     = NULL;
 
// attempt an asynchronous read operation
bResult = ReadFile(hFile, &inBuffer, nBytesToRead, &nBytesRead,
    &gOverlapped) ;
 
// if there was a problem, or the async. operation's still pending ...
if (!bResult)
{
    // deal with the error code
    switch (dwError = GetLastError())

    {
        case ERROR_HANDLE_EOF:
        {
            // we're reached the end of the file
            // during the call to ReadFile
 
            // code to handle that
        }
 
        case ERROR_IO_PENDING:
        {
            // asynchronous i/o is still in progress
 
            // do something else for a while
            GoDoSomethingElse() ;
 
            // check on the results of the asynchronous read
            bResult = GetOverlappedResult(hFile, &gOverlapped,

                &nBytesRead, FALSE) ;
 
            // if there was a problem ...
            if (!bResult)
            {
                // deal with the error code
                switch (dwError = GetLastError())
                {
                    case ERROR_HANDLE_EOF:
                    {
                        // we're reached the end of the file
                        //during asynchronous operation
                    }
 
                    // deal with other error cases

                }
            }
        } // end case
 
        // deal with other error cases
 
    } // end switch
} // end if
В моем примере придется чуть поправить в CreateFile. Полное описание данной функции:
Цитата
The CreateFile function creates or opens the following objects and returns a handle that can be used to access the object:

·   files
·   pipes
·   mailslots
·   communications resources
·   disk devices (Windows NT only)
·   consoles
·   directories (open only)

 

HANDLE CreateFile(

    LPCTSTR lpFileName,   // pointer to name of the file
    DWORD dwDesiredAccess,   // access (read-write) mode
    DWORD dwShareMode,   // share mode
    LPSECURITY_ATTRIBUTES lpSecurityAttributes,   // pointer to security attributes
    DWORD dwCreationDistribution,   // how to create
    DWORD dwFlagsAndAttributes,   // file attributes
    HANDLE hTemplateFile    // handle to file with attributes to copy 
   );   
 

Parameters

lpFileName

Points to a null-terminated string that specifies the name of the object (file, pipe, mailslot, communications resource, disk device, console, or directory) to create or open.

If *lpFileName is a path, there is a default string size limit of MAX_PATH characters. This limit is related to how the CreateFile function parses paths.
Windows NT: You can use paths longer than MAX_PATH characters by calling the wide (W) version of CreateFile and prepending "\\?\" to the path. The "\\?\" tells the function to turn off path parsing. This lets you use paths that are nearly 32,000 Unicode characters long. You must use fully-qualified paths with this technique. This also works with UNC names. The "\\?\" is ignored as part of the path. For example, "\\?\C:\myworld\private" is seen as "C:\myworld\private", and "\\?\UNC\tom_1\hotstuff\coolapps" is seen as "\\tom_1\hotstuff\coolapps".

dwDesiredAccess

Specifies the type of access to the object. An application can obtain read access, write access, read-write access, or device query access. This parameter can be any combination of the following values.

Value   Meaning
0   Specifies device query access to the object. An application can query device attributes without accessing the device.
GENERIC_READ   Specifies read access to the object. Data can be read from the file and the file pointer can be moved. Combine with GENERIC_WRITE for read-write access.
GENERIC_WRITE   Specifies write access to the object. Data can be written to the file and the file pointer can be moved. Combine with GENERIC_READ for read-write access.
 

dwShareMode

Set of bit flags that specifies how the object can be shared. If dwShareMode is 0, the object cannot be shared. Subsequent open operations on the object will fail, until the handle is closed.
To share the object, use a combination of one or more of the following values:

Value   Meaning
FILE_SHARE_DELETE   Windows NT only: Subsequent open operations on the object will succeed only if delete access is requested.
FILE_SHARE_READ   Subsequent open operations on the object will succeed only if read access is requested.
FILE_SHARE_WRITE   Subsequent open operations on the object will succeed only if write access is requested.
 

lpSecurityAttributes

Pointer to a SECURITY_ATTRIBUTES structure that determines whether the returned handle can be inherited by child processes. If lpSecurityAttributes is NULL, the handle cannot be inherited.

Windows NT: The lpSecurityDescriptor member of the structure specifies a security descriptor for the object. If lpSecurityAttributes is NULL, the object gets a default security descriptor. The target file system must support security on files and directories for this parameter to have an effect on files.
Windows 95: The lpSecurityDescriptor member of the structure is ignored.

 

dwCreationDistribution

Specifies which action to take on files that exist, and which action to take when files do not exist. For more information about this parameter, see the Remarks section. This parameter must be one of the following values:

Value   Meaning
CREATE_NEW   Creates a new file. The function fails if the specified file already exists.
CREATE_ALWAYS   Creates a new file. The function overwrites the file if it exists.
OPEN_EXISTING   Opens the file. The function fails if the file does not exist.
See the Remarks section for a discussion of why you should use the OPEN_EXISTING flag if you are using the CreateFile function for devices, including the console.
OPEN_ALWAYS   Opens the file, if it exists. If the file does not exist, the function creates the file as if dwCreationDistribution were CREATE_NEW.
TRUNCATE_EXISTING   Opens the file. Once opened, the file is truncated so that its size is zero bytes. The calling process must open the file with at least GENERIC_WRITE access. The function fails if the file does not exist.
 

dwFlagsAndAttributes

Specifies the file attributes and flags for the file.

Any combination of the following attributes is acceptable, except all other file attributes override FILE_ATTRIBUTE_NORMAL.

Attribute   Meaning
FILE_ATTRIBUTE_ARCHIVE   The file should be archived. Applications use this attribute to mark files for backup or removal.
FILE_ATTRIBUTE_COMPRESSED   The file or directory is compressed. For a file, this means that all of the data in the file is compressed. For a directory, this means that compression is the default for newly created files and subdirectories.
FILE_ATTRIBUTE_HIDDEN   The file is hidden. It is not to be included in an ordinary directory listing.
FILE_ATTRIBUTE_NORMAL   The file has no other attributes set. This attribute is valid only if used alone.
FILE_ATTRIBUTE_OFFLINE   The data of the file is not immediately available. Indicates that the file data has been physically moved to offline storage.
FILE_ATTRIBUTE_READONLY   The file is read only. Applications can read the file but cannot write to it or delete it.
FILE_ATTRIBUTE_SYSTEM   The file is part of or is used exclusively by the operating system.
FILE_ATTRIBUTE_TEMPORARY   The file is being used for temporary storage. File systems attempt to keep all of the data in memory for quicker access rather than flushing the data back to mass storage. A temporary file should be deleted by the application as soon as it is no longer needed.
 

Any combination of the following flags is acceptable.

Flag   Meaning
FILE_FLAG_WRITE_THROUGH   
Instructs the operating system to write through any intermediate cache and go directly to disk. The operating system can still cache write operations, but cannot lazily flush them.
FILE_FLAG_OVERLAPPED   
Instructs the operating system to initialize the object, so ReadFile, WriteFile, ConnectNamedPipe, and TransactNamedPipe operations that take a significant amount of time to process return ERROR_IO_PENDING. When the operation is finished, an event is set to the signaled state.
When you specify FILE_FLAG_OVERLAPPED, the ReadFile and WriteFile functions must specify an OVERLAPPED structure. That is, when FILE_FLAG_OVERLAPPED is specified, an application must perform overlapped reading and writing.
When FILE_FLAG_OVERLAPPED is specified, the operating system does not maintain the file pointer. The file position must be passed as part of the lpOverlapped parameter (pointing to an OVERLAPPED structure) to the ReadFile and WriteFile functions.
This flag also enables more than one operation to be performed simultaneously with the handle (a simultaneous read and write operation, for example).
FILE_FLAG_NO_BUFFERING   
Instructs the operating system to open the file with no intermediate buffering or caching. This can provide performance gains in some situations. An application must meet certain requirements when working with files opened with FILE_FLAG_NO_BUFFERING:·   File access must begin at byte offsets within the file that are integer multiples of the volume's sector size. ·   File access must be for numbers of bytes that are integer multiples of the volume's sector size. For example, if the sector size is 512 bytes, an application can request reads and writes of 512, 1024, or 2048 bytes, but not of 335, 981, or 7171 bytes. ·   Buffer addresses for read and write operations must be aligned on addresses in memory that are integer multiples of the volume's sector size. One way to align buffers on integer multiples of the volume sector size is to use VirtualAlloc to allocate the buffers. It allocates memory that is aligned on addresses that are integer multiples of the operating system's memory page size. Since both memory page and volume sector sizes are powers of 2, this memory is also aligned on addresses that are integer multiples of a volume's sector size. An application can determine a volume's sector size by calling the GetDiskFreeSpace function.
FILE_FLAG_RANDOM_ACCESS   
Indicates that the file is accessed randomly. Windows can use this as a hint to optimize file caching.
FILE_FLAG_SEQUENTIAL_SCAN   
Indicates that the file is to be accessed sequentially from beginning to end. Windows can use this as a hint to optimize file caching. If an application moves the file pointer for random access, optimum caching may not occur; however, correct operation is still guaranteed.
Specifying this flag can increase performance for applications that read large files using sequential access. Performance gains can be even more noticeable for applications that read large files mostly sequentially, but occasionally skip over small ranges of bytes.
FILE_FLAG_DELETE_ON_CLOSE   
Indicates that the operating system is to delete the file immediately after all of its handles have been closed, not just the handle for which you specified FILE_FLAG_DELETE_ON_CLOSE. Subsequent open requests for the file will fail, unless FILE_SHARE_DELETE is used.
FILE_FLAG_BACKUP_SEMANTICS   
Windows NT only: Indicates that the file is being opened or created for a backup or restore operation. The operating system ensures that the calling process overrides file security checks, provided it has the necessary permission to do so. The relevant permissions are SE_BACKUP_NAME and SE_RESTORE_NAME.You can also set this flag to obtain a handle to a directory. A directory handle can be passed to some Win32 functions in place of a file handle.
FILE_FLAG_POSIX_SEMANTICS   
Indicates that the file is to be accessed according to POSIX rules. This includes allowing multiple files with names, differing only in case, for file systems that support such naming. Use care when using this option because files created with this flag may not be accessible by applications written for MS-DOS, Windows, or Windows NT.
 

If the CreateFile function opens the client side of a named pipe, the dwFlagsAndAttributes parameter can also contain Security Quality of Service information. When the calling application specifies the SECURITY_SQOS_PRESENT flag, the dwFlagsAndAttributes parameter can contain one or more of the following values:

Value   Meaning
SECURITY_ANONYMOUS   Specifies to impersonate the client at the Anonymous impersonation level.
SECURITY_IDENTIFICATION   Specifies to impersonate the client at the Identification impersonation level.
SECURITY_IMPERSONATION   Specifies to impersonate the client at the Impersonation impersonation level.
SECURITY_DELEGATION   Specifies to impersonate the client at the Delegation impersonation level.
SECURITY_CONTEXT_TRACKING   Specifies that the security tracking mode is dynamic. If this flag is not specified, Security Tracking Mode is static.
SECURITY_EFFECTIVE_ONLY   Specifies that only the enabled aspects of the client's security context are available to the server. If you do not specify this flag, all aspects of the client's security context are available.This flag allows the client to limit the groups and privileges that a server can use while impersonating the client.
 

For more information, see Security.

hTemplateFile

Specifies a handle with GENERIC_READ access to a template file. The template file supplies file attributes and extended attributes for the file being created.
Windows 95: This value must be NULL. If you supply a handle under Windows 95, the call fails and GetLastError returns ERROR_NOT_SUPPORTED.

 

Return Values

If the function succeeds, the return value is an open handle to the specified file. If the specified file exists before the function call and dwCreationDistribution is CREATE_ALWAYS or OPEN_ALWAYS, a call to GetLastError returns ERROR_ALREADY_EXISTS (even though the function has succeeded). If the file does not exist before the call, GetLastError returns zero.
If the function fails, the return value is INVALID_HANDLE_VALUE. To get extended error information, call GetLastError.

Remarks

Use the CloseHandle function to close an object handle returned by CreateFile.
As noted above, specifying zero for dwDesiredAccess allows an application to query device attributes without actually accessing the device. This type of querying is useful, for example, if an application wants to determine the size of a floppy disk drive and the formats it supports without having a floppy in the drive.

Files

When creating a new file, the CreateFile function performs the following actions:

·   Combines the file attributes and flags specified by dwFlagsAndAttributes with FILE_ATTRIBUTE_ARCHIVE.
·   Sets the file length to zero.
·   Copies the extended attributes supplied by the template file to the new file if the hTemplateFile parameter is specified.

 

When opening an existing file, CreateFile performs the following actions:

·   Combines the file flags specified by dwFlagsAndAttributes with existing file attributes. CreateFile ignores the file attributes specified by dwFlagsAndAttributes.
·   Sets the file length according to the value of dwCreationDistribution.
·   Ignores the hTemplateFile parameter.
·   Ignores the lpSecurityDescriptor member of the SECURITY_ATTRIBUTES structure if the lpSecurityAttributes parameter is not NULL. The other structure members are used. The bInheritHandle member is the only way to indicate whether the file handle can be inherited.

 

If you are attempting to create a file on a floppy drive that does not have a floppy disk or a CD-ROM drive that does not have a CD, the system displays a message box asking the user to insert a disk or a CD, respectively. To prevent the system from displaying this message box, call the SetErrorMode function with SEM_FAILCRITICALERRORS.

Pipes

If CreateFile opens the client end of a named pipe, the function uses any instance of the named pipe that is in the listening state. The opening process can duplicate the handle as many times as required but, once opened, the named pipe instance cannot be opened by another client. The access specified when a pipe is opened must be compatible with the access specified in the dwOpenMode parameter of the CreateNamedPipe function. For more information about pipes, see Pipes.

Mailslots

If CreateFile opens the client end of a mailslot, the function returns INVALID_HANDLE_VALUE if the mailslot client attempts to open a local mailslot before the mailslot server has created it with the CreateMailSlot function. For more information about mailslots, see Mailslots.

Communications Resources

The CreateFile function can create a handle to a communications resource, such as the serial port COM1. For communications resources, the dwCreationDistribution parameter must be OPEN_EXISTING, and the hTemplate parameter must be NULL. Read, write, or read-write access can be specified, and the handle can be opened for overlapped I/O. For more information about communications, see Communications.
Disk Devices
Windows NT: You can use the CreateFile function to open a disk drive or a partition on a disk drive. The function returns a handle to the disk device; that handle can be used with the DeviceIOControl function. The following requirements must be met in order for such a call to succeed:

·   The caller must have administrative privileges for the operation to succeed on a hard disk drive.
·   The lpFileName string should be of the form \\.\PHYSICALDRIVEx to open the hard disk x. Hard disk numbers start at zero. For example:

String   Meaning
\\.\PHYSICALDRIVE2   Obtains a handle to the third physical drive on the user's computer.
 

·   The lpFileName string should be \\.\x: to open a floppy drive x or a partition x on a hard disk. For example:

String   Meaning
\\.\A:   Obtains a handle to drive A on the user's computer.
\\.\C:   Obtains a handle to drive C on the user's computer.
 

Windows 95: This technique does not work for opening a logical drive. In Windows 95, specifying a string in this form causes CreateFile to return an error.

·   The dwCreationDistribution parameter must have the OPEN_EXISTING value.
·   When opening a floppy disk or a partition on a hard disk, you must set the FILE_SHARE_WRITE flag in the dwShareMode parameter.

 

Consoles

The CreateFile function can create a handle to console input (CONIN$). If the process has an open handle to it as a result of inheritance or duplication, it can also create a handle to the active screen buffer (CONOUT$). The calling process must be attached to an inherited console or one allocated by the AllocConsole function. For console handles, set the CreateFile parameters as follows:

Parameters   Value
lpFileName   Use the CONIN$ value to specify console input and the CONOUT$ value to specify console output.
CONIN$ gets a handle to the console's input buffer, even if the SetStdHandle function redirected the standard input handle. To get the standard input handle, use the GetStdHandle function.
CONOUT$ gets a handle to the active screen buffer, even if SetStdHandle redirected the standard output handle. To get the standard output handle, use GetStdHandle.
dwDesiredAccess   GENERIC_READ | GENERIC_WRITE is preferred, but either one can limit access.
dwShareMode   If the calling process inherited the console or if a child process should be able to access the console, this parameter must be FILE_SHARE_READ | FILE_SHARE_WRITE.
lpSecurityAttributes   If you want the console to be inherited, the bInheritHandle member of the SECURITY_ATTRIBUTES structure must be TRUE.
dwCreationDistribution   You should specify OPEN_EXISTING when using CreateFile to open the console.
dwFlagsAndAttributes   Ignored.
hTemplateFile   Ignored.
 

The following list shows the effects of various settings of fwdAccess and lpFileName.

lpFileName   fwdAccess   Result
CON   GENERIC_READ   Opens console for input.
CON   GENERIC_WRITE   Opens console for output.
CON   GENERIC_READ\
GENERIC_WRITE   Windows 95: Causes CreateFile to fail; GetLastError returns ERROR_PATH_NOT_FOUND.Windows NT:  Causes CreateFile to fail; GetLastError returns ERROR_FILE_NOT_FOUND.
 

Directories

An application cannot create a directory with CreateFile; it must call CreateDirectory or CreateDirectoryEx to create a directory.

Windows NT:

You can obtain a handle to a directory by setting the FILE_FLAG_BACKUP_SEMANTICS flag. A directory handle can be passed to some Win32 functions in place of a file handle.

Some file systems, such as NTFS, support compression for individual files and directories. On volumes formatted for such a file system, a new directory inherits the compression attribute of its parent directory.

Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #17 : 06-04-2005 18:27 » 

ок обьясни пожалуйста как мне буфер создать  почему у меня не читает так ?
Код:
void __fastcall TForm1::ReadClick(TObject *Sender)
{

DWORD temp;
String str;
ReadFile(hSlot,&str,425,&temp,NULL);
Memo1->Text = str;


}
Создан      вот так
         
Код:
 
 HANDLE hSlot = CreateMailslot("\\.\mailslot\msgChat",
                               0,MAILSLOT_WAIT_FOREVER, NULL);
и вот так
Код:
if(hSlot){
HANDLE hFile=CreateFile( "\\.\mailslot\msgChat",
                             GENERIC_WRITE,FILE_SHARE_READ,NULL,
                             OPEN_EXISTING,FILE_ATTRIBUTE_NORMAL,NULL);
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #18 : 06-04-2005 18:44 » 

String str; Это хоть и строка. Но ее нельзя вставлять в ReadFile(hSlot,&str,425,&temp,NULL); Потому что, Она имеет совсем другую структуру. По идее компилятор должен не пропустить это. Из за несоответствия типов.
И еше один момент. Размер строки изменяется автоматически. т.е. нулевая строка имеет нулевой размер. И работать с ней в обход инструментов строки чревато последствиями.
Буфер можно создавать как я показал выше.
Код:
#define MAXBUF 1024

char buf[MAXBUF];
Здесь ты заранее выделил под буфер 1024 байта. И можеш спокойно работать с ним.
« Последнее редактирование: 06-04-2005 18:46 от Finch » Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #19 : 06-04-2005 19:07 » 

а читает не корректно посылаю строку Message  полуяаю B¦@P&#242;
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #20 : 06-04-2005 19:08 » 

Где именно? Это выводится на экран?
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #21 : 06-04-2005 20:01 » 

Код:
DWORD temp;
char buf[maxbuf];
ReadFile(hSlot,&buf,425,&temp,NULL);
Memo1->Text=buf;
Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #22 : 06-04-2005 21:32 » 

reconnector, buf это Нуль терминальная строка. Memo1->Text это AnsiString. Строки в Си вообше так нельзя приравнивать. А тем более разных типов. Есть заветная клавиша F1 поиши AnsiString. И почитай, какая функция преобразовывает из нуль терминальной строки в AnsiString
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #23 : 07-04-2005 12:00 » 

Сегодня ночью не заметил. С TMemo Нужно работать так. Memo1->Lines->Add(AnsiString(buf)); Код точно не проверил. Сегодня вечером проверю.
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #24 : 08-04-2005 17:57 » 

И так как ты говорил и так
Код:

char buf[maxbuf];
ReadFile(hSlot,buf,425,&temp,NULL);
Memo1->Lines->SetText(buf);

 не читает Жаль   может не в Memo     выводить результат ?
« Последнее редактирование: 08-04-2005 17:59 от reconnector » Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #25 : 08-04-2005 18:11 » 

Попробуй поставить после ReadFile(hSlot,buf,425,&temp,NULL); Брэкпоинт. И посмотри что содержится в буфере.
Если нормальная строка. Будем дальше искать. Если Муть то иши ошибку с источника заполнения буфера. Т.е. почему ReadFile не работает нормально.
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #26 : 08-04-2005 18:34 » 

Поставил точку останова чтоб выполнялось до
того как это 
Код:
Memo1->Lines->SetText(buf);
все выведется до чтения а в Memo  все равно иероглифы появляются   

Я думаю не читает он вообще
« Последнее редактирование: 08-04-2005 18:36 от reconnector » Записан
Finch
Спокойный
Администратор

il
Offline Offline
Пол: Мужской
Пролетал мимо


« Ответ #27 : 08-04-2005 18:42 » 

В маилслотах я не волоку. Не встречались такие задачи. Поэтому извиняйте. Улыбаюсь
Записан

Не будите спашяго дракона.
             Джаффар (Коша)
reconnector
Гость
« Ответ #28 : 08-04-2005 18:42 » 

Код:
if(ReadFile(hSlot,buf,425,&temp,NULL)==NULL) {ShowMessage("NULL");}
Возвратила Ноль  или может как-нибудь по др проверить ?
Записан
reconnector
Гость
« Ответ #29 : 10-04-2005 08:44 » 

Вoт если интересно нашел в примерах
Код:
bool SendNetMessage(AnsiString Komp, AnsiString Mes)
{
AnsiString From;
char CompName[10];
DWORD size=10;

if(!GetComputerName(CompName,&size)) return false;
From=CompName;
if(Mes.Length()==0) return false;
HANDLE hSlot = CreateFile(("\\\\"+Komp+"\\mailslot\\messngr").c_str(),
GENERIC_WRITE, FILE_SHARE_READ, NULL,
OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
if (hSlot == INVALID_HANDLE_VALUE) return false;
DWORD cb=0;
BOOL ret;
char *buf=new char[From.Length()+1+Komp.Length()+1+Mes.Length()+1];
//1. From
memcpy(&buf[cb],From.c_str(),From.Length()+1);
cb +=From.Length()+1; //+1 на конце должен быть 0
//2. To
memcpy(&buf[cb],Komp.c_str(),Komp.Length()+1);
cb +=Komp.Length()+1;

memcpy(&buf[cb],Mes.c_str(),Mes.Length()+1);
cb +=Mes.Length()+1;
//ConvertToDos
CharToOemBuff(buf,buf,cb);
ret=WriteFile(hSlot, buf,cb, &cb, NULL);
CloseHandle(hSlot);
delete[] buf;
if(!ret) return false;
return true;
}

void __fastcall TForm1::Button1Click(TObject *Sender)
{
AnsiString Komp,Mes;

Komp=Edit1->Text;
Mes=Edit2->Text; //Message
bool ret;
int Kol=UpDown1->Position;
for(int i=1;i<=Kol;i++)
{
ret=SendNetMessage(Komp,Mes);
}
}

« Последнее редактирование: 30-11-2007 21:11 от Алексей1153++ » Записан
Страниц: [1] 2  Все   Вверх
  Печать  
 

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines