search for: literal

...tefaniuc (80): dswave: Simplify the stub WAVE IPersistStream_Load(). gdiplus: Remove superfluous cast to self. shell32: Remove superfluous cast to self. shlwapi: Remove superfluous cast to self. oleaut32: Remove superfluous casts. atl80/tests:Use wide-char string literals. browseui: Use wide-char string literals. d2d1/tests:Use wide-char string literals. comcat/tests: Use wide-char string literals. comsvcs/tests: Use wide-char string literals. d3dx10/tests: Use wide-char string literals. d3dx11/tests: Use wide-char string literal...

> On Wed, 14 Jun 2017, G?bor Cs?rdi wrote: > > > I like the idea of string literals, but the C/C++ way clearly does not > > work. The Python/Julia way might, i.e.: > > > > """this is a > > multi-line > > lineral""" > > luke-tierney at uiowa.edu: > This does look like a promising option; some more careful check...

...e not available and will be skipped: PrinterDC src/AboutDialogInfo.cpp:1776:20: error: rubyio.h: No such file or directory src/AboutDialogInfo.cpp: In function ''VALUE _wrap_wxAboutDialogInfo_SetName(int, VALUE*, VALUE)'': src/AboutDialogInfo.cpp:1856: warning: format not a string literal and no format arguments src/AboutDialogInfo.cpp: In function ''VALUE _wrap_wxAboutDialogInfo_GetName(int, VALUE*, VALUE)'': src/AboutDialogInfo.cpp:1882: warning: format not a string literal and no format arguments src/AboutDialogInfo.cpp:1886: error: ''rb_utf8_encoding'...

...ial: 1/1,0, assert 0 initial: 0/0, assert 0 initial: 0/0, assert 0 - final state 30370718 + final state 110cba530 tre_compile: parsing '(^|[^%])(%%)*%V' AST: catenation, sub 0, 0 tags @@ -177,7 +177,7 @@ assertions: bol union, sub -1, 0 tags literal (, $) (0, 36), pos 0, sub -1, 0 tags - literal (&, M-^?) (38, 65535), pos 0, sub -1, 0 tags + literal (&, M-^?) (38, -1), pos 0, sub -1, 0 tags iteration {0, -1}, sub -1, 0 tags, greedy catenation, sub 2, 0 tags literal (%, %) (37, 37), p...

Hello - When using the stats option I understand that Literal should be the amount of data that did not match, and that Sent should be the actually amount of bytes that were sent. I always use compress for remote transfers, so I'm used to Sent being smaller (usually around half the size) than Literal. However on one server, the backup from last night had...

...le that resides within an absolute path containing a ':' character. Ala, "tftp foobar -c get C:2/tftpdir/myfile". Since the tftp client automatically converts the host:file syntax, I get an error "tftp: C: Unknown host". I made a chage to the tftp client code to add a literal mode (-l), that prevents the special treatment of the ':' character. I've attached a patch set for main.c and tftp.1.in for your consideration. I'm not sure how many folks run into this, but it may be somewhat common for VxWorks and perhaps MSDOS users. Thanks, Craig Johnston ***...

...assert 0 >> - final state 30370718 >> + final state 110cba530 >> tre_compile: parsing '(^|[^%])(%%)*%V' >> AST: >> catenation, sub 0, 0 tags >> @@ -177,7 +177,7 @@ >> assertions: bol >> union, sub -1, 0 tags >> literal (, $) (0, 36), pos 0, sub -1, 0 tags >> - literal (&, M-^?) (38, 65535), pos 0, sub -1, 0 tags >> + literal (&, M-^?) (38, -1), pos 0, sub -1, 0 tags >> iteration {0, -1}, sub -1, 0 tags, greedy >> catenation, sub 2, 0 tags >>...

...r/lib/gcc-lib/i386-redhat-linux/3.2/include -DKBUILD_BASENAME=nfnetlink -DEXPORT_SYMTAB -c nfnetlink.c cc1: warning: -malign-functions is obsolete, use -falign-functions nfnetlink.c: In function `nfnetlink_subsys_register_Re3f406ed': nfnetlink.c:85: warning: concatenation of string literals with __FUNCTION__ is deprecated nfnetlink.c: In function `nfnetlink_subsys_unregister_Re44f401f': nfnetlink.c:97: warning: concatenation of string literals with __FUNCTION__ is deprecated nfnetlink.c: In function `nfnetlink_find_client': nfnetlink.c:123: warning: concatenation...

...:64:64-S128-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f16:16:16-f32:32:32-f64:64:64-f128:128:128-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64" ; Function Attrs: nounwind readnone define i32 @"main(int)"(i32 %i, i32* nocapture %hidden) #0 { entry: %"Array literal space" = alloca [5 x i32], align 4 %0 = getelementptr [5 x i32]* %"Array literal space", i64 0, i64 0 store i32 1, i32* %0, align 4 %1 = getelementptr [5 x i32]* %"Array literal space", i64 0, i64 1 store i32 2, i32* %1, align 4 %2 = getelementptr [5 x i32]*...

...tringRefs to avoid static initializers for global tables of/containing StringRefs. Creating constexpr StringRefs isn't trivial as strlen isn't portably constexpr and std::char_traits<char>::length is only constexpr in C++17. Alp Toker tried to create constexpr StringRefs for strings literals by subclassing StringRef: https://reviews.llvm.org/rL200187 This is a verbose change where needed at string literal call sites. Mehdi AMINI tried to add a constexpr constructor for string literals by making the constructor from const char * explicit: https://reviews.llvm.org/D25639 This is a verb...

On 16/06/2017 2:04 PM, Radford Neal wrote: >> On Wed, 14 Jun 2017, G?bor Cs?rdi wrote: >> >>> I like the idea of string literals, but the C/C++ way clearly does not >>> work. The Python/Julia way might, i.e.: >>> >>> """this is a >>> multi-line >>> lineral""" >> >> luke-tierney at uiowa.edu: > >> This does look like a promising o...

...le that resides within an absolute path containing a ':' character. Ala, "tftp foobar -c get C:2/tftpdir/myfile". Since the tftp client automatically converts the host:file syntax, I get an error "tftp: C: Unknown host". I made a chage to the tftp client code to add a literal mode (-l), that prevents the special treatment of the ':' character. I've attached a patch set for main.c and tftp.1.in for your consideration. I'm not sure how many folks run into this, but it may be somewhat common for VxWorks and perhaps MSDOS users. Thanks, Craig Johnston **...

...l Provider'. IMAP: 08:53:03 [db] OnNotify: asOld = 4, asNew = 6, ae = 2 IMAP: 08:53:03 [db] OnNotify: asOld = 6, asNew = 6, ae = 4 IMAP: 08:53:03 [db] OnNotify: asOld = 6, asNew = 5, ae = 2 IMAP: 08:53:04 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 08:53:04 [rx] * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. IMAP: 08:53:04 [tx] ozzj CAPABILITY IMAP: 08:53:04 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 08:53:04 [rx] * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN IMAP: 08:53:0...

Hi all Currently tablegen parses binary literals such as 0b011 and immediately turns them in to integers internally. Due to this, 0b011 is a 2-bit value because tablegen will happily drop leading zeroes on integers. I propose that we change this, and store binary literals with a size. I think this is much more natural, as when the user writes...

(forgot to CC llvmdev) On Thu, Mar 21, 2013 at 5:54 PM, Alexander Potapenko <glider at google.com> wrote: > Hey Anna, Nick, Ted, > > We've the following problem with string literals under ASan on Mac. > Some global string constants end up being put into the .cstring > section, for which the following rules apply: > - the strings can't contain zeroes in their bodies > - the link editor places only one copy of each literal into the > output file's secti...

...where > besides the end of the section when there is no .ltorg directive. > > Here is the relevant section from the gcc docs > (https://sourceware.org/binutils/docs/as/ARM-Directives.html): > > """ > .ltorg > This directive causes the current contents of the literal pool to be dumped > into the current section (which is assumed to be the .text section) at the > current location (aligned to a word boundary). GAS maintains a separate > literal pool for each section and each sub-section. The .ltorg directive > will only affect the literal pool of the...

Alexander, On Darwin the "__cstring" section (really section with type S_CSTRING_LITERAL) is defined to contain zero terminate strings of bytes that the linker can merge and re-order. If you want pad bytes before and after the string, you need to put the strings in a different section (e.g. __TEXT, __const). But, CF/NSString literals will be problematic. The compiler emits a static...

...l Provider'. IMAP: 08:53:03 [db] OnNotify: asOld = 4, asNew = 6, ae = 2 IMAP: 08:53:03 [db] OnNotify: asOld = 6, asNew = 6, ae = 4 IMAP: 08:53:03 [db] OnNotify: asOld = 6, asNew = 5, ae = 2 IMAP: 08:53:04 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 08:53:04 [rx] * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. IMAP: 08:53:04 [tx] ozzj CAPABILITY IMAP: 08:53:04 [db] OnNotify: asOld = 5, asNew = 5, ae = 3 IMAP: 08:53:04 [rx] * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN IMAP: 08:53:0...

On Wed, 14 Jun 2017 06:12:09 -0500, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 14/06/2017 5:58 AM, Andreas Kersting wrote: > > Hi, > > > > I would really like to have a way to split long string literals across > > multiple lines in R. > > I don't understand why you require the string to be a literal. Why not > construct the long string in an expression like > > paste0("aaa", > "bbb") > > ? Surely the execution time of the past...

...al state 110cba530 >>>> tre_compile: parsing '(^|[^%])(%%)*%V' >>>> AST: >>>> catenation, sub 0, 0 tags >>>> @@ -177,7 +177,7 @@ >>>> assertions: bol >>>> union, sub -1, 0 tags >>>> literal (, $) (0, 36), pos 0, sub -1, 0 tags >>>> - literal (&, M-^?) (38, 65535), pos 0, sub -1, 0 tags >>>> + literal (&, M-^?) (38, -1), pos 0, sub -1, 0 tags >>>> iteration {0, -1}, sub -1, 0 tags, greedy >>>> cat...