search for: udls

...s a summary of (most) everything contained in this patch: > > 1) UDL Syntax for outputting to a stream or converting to a string. > outs() << "{0}"_fmt.stream(1) > std::string S = "{0}"_fmt.string(1); > I continue to have a strong objection to using UDLs for this (or anything else in LLVM). I think this feature is poorly known by many programmers. I think it will produce error messages that are confusing and hard to debug. I think it will have a significant negative impact on compile time. I also think that it will exercise substantially less well...

...ck i had seen so far seemed to prefer UDL syntax due to the brevity and similarity to Python. I recall you mentioned the verbosity of llvm format as something you would like to see this improve, so i had assumed you would be happy with UDL syntax. compile time checking may not be possible without UDLs unless we wrap the format string in a macro, which may hurt readability even more. With a UDL we can get it via the gnu literal operator template though, and the check can be #ifdef'ed out on any compiler that doesn't support that extension In any case, both syntaxes are currently supporte...

I have a program statreporting. In Windows it connects to SQL server by udl file. May I use udl in wine. I install MDAC by winetricks. But udl doesn't see sql server. Help me, please!

I have a problem with one application that using UDL file as a source to database. I have installed MDAC2.8 jet4, and changed DLL-s odbc32, odbccp32, oledb32 to native version. In odbcad32.exe I have created data source with the same configuration like in udl file and it's working. How to open UDL file for edition in wine (no text file edition)? Some ideas why it is not working?

char buffer[100]; And it also allows LIT(buffer) to compile, whereas the UDL doesn't. On Tue, Nov 29, 2016 at 9:54 AM Mehdi Amini <mehdi.amini at apple.com> wrote: > > > On Nov 29, 2016, at 9:52 AM, Malcolm Parsons <malcolm.parsons at gmail.com> > wrote: > > > > On 29 November 2016 at 17:38, Zachary Turner <zturner at google.com> wrote: > >>

--- drivers/gpu/drm/udl/udl_encoder.c | 8 -------- 1 file changed, 8 deletions(-) diff --git a/drivers/gpu/drm/udl/udl_encoder.c b/drivers/gpu/drm/udl/udl_encoder.c index a181a64..59a4b34 100644 --- a/drivers/gpu/drm/udl/udl_encoder.c +++ b/drivers/gpu/drm/udl/udl_encoder.c @@ -26,13 +26,6 @@ static void udl_encoder_disable(struct drm_encoder *encoder) { } -static bool udl_mode_fixup(struct

...ing contained in this patch: >> >> 1) UDL Syntax for outputting to a stream or converting to a string. >> outs() << "{0}"_fmt.stream(1) >> std::string S = "{0}"_fmt.string(1); >> > > I continue to have a strong objection to using UDLs for this (or anything > else in LLVM). > > I think this feature is poorly known by many programmers. I think it will > produce error messages that are confusing and hard to debug. I think it > will have a significant negative impact on compile time. I also think that > it will exe...

...ry of (most) everything contained in this patch: > > 1) UDL Syntax for outputting to a stream or converting to a string. > outs() << "{0}"_fmt.stream(1) > std::string S = "{0}"_fmt.string(1); > > > I continue to have a strong objection to using UDLs for this (or anything > else in LLVM). > > I think this feature is poorly known by many programmers. I think it will > produce error messages that are confusing and hard to debug. I think it > will have a significant negative impact on compile time. I also think that > it will exe...

On 29 November 2016 at 17:38, Zachary Turner <zturner at google.com> wrote: > I see, but I looked over your proposed implementation from earlier in the > thread, and if I'm not mistaken I see this: That's a different suggestion. > That said, what did you think about my other proposal of the complicated UDL > with macro? > > #define LIT(x) x_string_ref_literal >

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (17): drm/virtio: removed optional dummy encoder mode_fixup function. drm/udl: removed optional

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (17): drm/virtio: removed optional dummy encoder mode_fixup function. drm/udl: removed optional

Hi all, There is a desire to be able to create constexpr StringRefs 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:

Ahh, UDLs also wouldn't permit non literal format strings, which is a deal breaker imo On Wed, Oct 12, 2016 at 7:03 AM Zachary Turner <zturner at google.com> wrote: > I'm not sure that would work well. The implementation relies on being able > to index into the parameter pack. How would...

...Because all that's going to happen is someone is going to resort to using snprintf etc, which is exactly the problem I'm trying to solve. It's literally no extra effort to support runtime format strings, and it makes the library more flexible as a result. I'm willing to start with UDLs only because I think it will get us quite far, but as soon as I need to pass a format string through an intermediate function or something like that, I will probably check in the 3 extra lines of code to add a const char* overload format function. FWIW, there's no easy way to add compile time...

The fact that the templatized constructor falls down because of the possibility of initializing StringRef with a stack-allocated char array kills that idea in my mind. I feel like the only two reasonable solutions are 1) allow UDL for this case, document that this is an exception and that UDLs are still not permitted anywhere else, and require (by policy, since I don't know of a way to have the compiler force it) that this UDL be used only in global constructors. One idea to help "enforce" this policy would be to give the UDL a ridiculously convoluted name, like `string_re...

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (17): drm/virtio: removed optional dummy encoder mode_fixup function. drm/udl: removed optional

mode_fixup function for encoder drivers became optional with patch http://patchwork.freedesktop.org/patch/msgid/1455106522-32307-1-git-send-email-palminha at synopsys.com This patch set nukes all the dummy mode_fixup implementations. (made on top of Daniel topic/drm-misc branch) Carlos Palminha (17): drm/virtio: removed optional dummy encoder mode_fixup function. drm/udl: removed optional

Steve Frampton [mailto:frampton@j-com.co.jp] of your address change Content-Length: 7142 samba@samba.org David Barroso <h4371719@alumnes.eup.udl.es> Jeremy Allison <jeremy@valinux.com> "Tulipant Gergely" <tulipant-gergely@dbrt.hu> Edwards Philip M Contr AFRL/SNRR <Philip.Edwards@wpafb.af.mil> Drenning Bruce <bdrenni@catholicrelief.org> Glenn

...uot; >> 2. os << format_string("{0}", 7); // writes "7" > > > The "<< format_string(..." is ... really verbose for me. It also makes me > strongly feel like this produces a string rather than a streamable entity. I wonder if we could use UDLs instead? os << "Test" << "{0}"_fs << 7; ~Aaron > > I'm not a huge fan of streaming, but if we want to go this route, I'd very > much like to keep the syntax short and sweet. "format" is pretty great for > that. If this is going...

..... Args) { > dbgs().format(Format, ConvertArg(Args)...); > } > > On Wed, Oct 12, 2016 at 11:24 AM Mehdi Amini <mehdi.amini at apple.com> > wrote: > > On Oct 12, 2016, at 7:12 AM, Zachary Turner via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Ahh, UDLs also wouldn't permit non literal format strings, which is a deal > breaker imo > > > Why? > Somehow the goal pursued by Pavel (which you didn’t object per-se) is to > provide *compile* time checking. > This imply that you cannot decouple the construction of the format and t...