Displaying 5 results from an estimated 5 matches for "esuccessfully".
Did you mean:
successfully
2011 Aug 06
0
specifying 'root' for mboot.c32/syslinux
I'm currently trying to integrate ReactOS's bootloader into my concept
bootdisk with standard layout. It uses Syslinux 4.10pre15.
This is failing on two parts:
1) bootsector method only works if specifying huge cluster size (16KB)
2) Multiboot method fails due to opening bootloader's configuration file
from harddisk instead of bootdisk.
2004 May 03
0
Windows XP client - intermittent 'network name cannot befound' loading profile
...d the HowTo verbatim. I have several problems that
are show-stoppers.
(1) I can�ft print. I have a hp Photosmart 7150 installed locally on
the
linux box and it works perfectly when printing from linux. I can see the
printer from the samba share in windows and can install and
�esuccessfully�f print (the job reads �gremote
downlevel document�h
Status: spooling User:nobody) but nothing prints. Lpq says:
Photosmart7150 is ready
No entries
Zero activity on the printers part.
(2) I can�ft access my share. If I try to go to start�?run...
2016 Feb 03
2
[RFC] Error handling in LLVM libraries.
Hi Mehdi,
> For a generic error class it is not an option indeed, but I was looking
at it in the context of LLVM internal use, so just like our RTTI is not an
option for “generic RTTI” but fits our need, we could (not should) do the
same with ErrorHandling.
Definitely. If this was LLVM only there'd be a strong case for using the
existing RTTI system. The reason for the new RTTI system is
2016 Feb 03
2
[RFC] Error handling in LLVM libraries.
Hi Mehdi,
> Side question on the related work because I’m curious: did you look for
similar generic scheme for error handling offered by other C++ libraries?
Maybe the common scheme is to use C++ exceptions but since many folks
disable them (hello Google ;-) ) there has been probably many other
attempts to address this.
I did look around, but not very hard. Among the people I asked, everyone
2016 Feb 03
6
[RFC] Error handling in LLVM libraries.
Hi Mehdi,
> If you subclass a diagnostic right now, isn’t the RTTI information
available to the handler, which can then achieve the same dispatching /
custom handling per type of diagnostic?
> (I’m not advocating the diagnostic system, which I found less convenient
to use than what you are proposing)
I have to confess I haven't looked at the diagnostic classes closely. I'll
take a