Welcome to the Lounge

emplate<typename Callback>
void ReadString(String^ fileName, Callback func)
{
  StorageFolder^ item = KnownFolders::PicturesLibrary;

  auto getFileOp = item->GetFileAsync(fileName);
  getFileOp->Completed = ref new AsyncOperationCompletedHandler<StorageFile^>
    ([=](IAsyncOperation<StorageFile^>^ operation, AsyncStatus status)
  {
    auto storageFile = operation->GetResults();
    auto openOp = storageFile->OpenAsync(FileAccessMode::Read);
    openOp->Completed = 
      ref new AsyncOperationCompletedHandler <IRandomAccessStream^>
      ([=](IAsyncOperation<IRandomAccessStream^>^ operation, AsyncStatus status)
    {
      auto istream = operation->GetResults();
      auto reader = ref new DataReader(istream);
      auto loadOp = reader->LoadAsync(istream->Size);
      loadOp->Completed = ref new AsyncOperationCompletedHandler<UINT>
        ([=](IAsyncOperation<UINT>^ operation, AsyncStatus status)
      {
        auto bytesRead = operation->GetResults();
        auto str = reader->ReadString(bytesRead);
        func(str);
      });
    });
  });
}

Marc Clifton wrote:

And then of course, the huge issue -- having to remember to delete objects! Having automated garbage collection is just so nice

Nish Sivakumar wrote:

Well, once you get used to unique_ptr and shared_ptr, that should take care of that issue

CDP1802 wrote:

I prefer A well written header file over a single ASP .Net page with 1000+ lines JavaScript and 3500 lines code behind.

CDP1802 wrote:

In most cases it turns out that I just have to write 'delete oSomeStuff' instead of 'someStuff.Dispose()'. If that's all.

Marc Clifton wrote:

give me back my first car in the same condition it was in when I gave it away. Functional, does the job, etc., but old and clunky.

Nish Sivakumar wrote:

Marc's boring analogy