similar to: [LLVMdev] path concatenation via operator

On 25.11.2010 23:56, Michael Spencer wrote: > On Nov 25, 2010, at 5:01 PM, Jochen Wilhelmy <j.wilhelmy at arcor.de > <mailto:j.wilhelmy at arcor.de>> wrote: > >> Hi! >> >> Of course nobody wants to implement unicode support for windows >> because windows should support an utf8-locale and windows is obsolete >> anyway ;-) >> >> But

On Nov 25, 2010, at 5:01 PM, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > Hi! > > Of course nobody wants to implement unicode support for windows > because windows should support an utf8-locale and windows is obsolete > anyway ;-) > > But there is a simple solution: use boost::filesystem::path everywhere you > use file names and paths, for example in

On Fri, Nov 26, 2010 at 4:00 AM, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > No, this post was prompted since I switched to boost::filesystem version 3 > in my own code and llvm/clang 2.8 > was the only lib with no unicode support on windows. > Will your code be api compatible to boost::filesystem? No. boost::filesystem makes extensive use of exceptions, which LLVM is

On Fri, 26 Nov 2010 09:28:17 -0500 Michael Spencer <bigcheesegs at gmail.com> wrote: > On Fri, Nov 26, 2010 at 4:00 AM, Jochen Wilhelmy > <j.wilhelmy at arcor.de> wrote: > > No, this post was prompted since I switched to boost::filesystem > > version 3 in my own code and llvm/clang 2.8 > > was the only lib with no unicode support on windows. > > Will your

Hi! Of course nobody wants to implement unicode support for windows because windows should support an utf8-locale and windows is obsolete anyway ;-) But there is a simple solution: use boost::filesystem::path everywhere you use file names and paths, for example in clang::FileManager::getFile. With version 3 opening a file is easy: std::fstream file(path.c_str()). Internally

Hello Jochen- Your expectation is incorrect, I'm afraid. Typically this would be expanded to something like this: … %cmp = … br i1 %cmp, label %ternary.true, label %ternary.false ternary.true: %truevalue = … br label %ternary.end ternary.false: %falsevalue = … br label %ternary.end ternary.end: %value = phi %type [%truevalue, %ternary.true], [%falsevalue,

2010/11/26 Jochen Wilhelmy <j.wilhelmy at arcor.de>: > >> Can't you just store filenames as UTF8 (like you do on Linux), and >> convert UTF8 to widechar just when calling the windows APIs? >> Same for converting back directory listings as such, you get widechar, >> and convert back to UTF8. >> All you would need to do is implement that conversion in

> Can't you just store filenames as UTF8 (like you do on Linux), and > convert UTF8 to widechar just when calling the windows APIs? > Same for converting back directory listings as such, you get widechar, > and convert back to UTF8. > All you would need to do is implement that conversion in System/Win32, > I think MultiByteToWideChar supports UTF8, doesn't it? > I

Hi Joshua, On 06/16/2015 03:32 PM, Joshua Bradley wrote: > Hi, first time poster here. During my time using R, I have always found > string concatenation to be (what I feel is) unnecessarily complicated by > requiring the use of the paste() or similar commands. > > > When searching for how to concatenate strings in R, several top search > results show answers that say to

> The reason for this is that C requires that only the value which is needed > is evaluated. If one of the selected values has a side effect, this becomes significant. > Ah, I see. But in my case I have only normal variables (local or global), no volatile and no functions. Therefore I wonder why the optimizer misses it in some cases (with globals). -Jochen

On Jun 16, 2015 3:44 PM, "Joshua Bradley" <jgbradley1 at gmail.com> wrote: > > Hi, first time poster here. During my time using R, I have always found > string concatenation to be (what I feel is) unnecessarily complicated by > requiring the use of the paste() or similar commands. I don't follow. In what sense is paste complicated to use? Not in the sense of

Gabor Csardi writes: > Btw. for some motivation, here is a (surely incomplete) list of > languages with '+' as the string concatenation operator: > > ALGOL 68, BASIC, C++, C#, Cobra, Pascal, Object Pascal, Eiffel, Go, > JavaScript, Java, Python, Turing, Ruby, Windows Powers hell, > Objective-C, F#, Sc-ala, Ya. The situation for R is rather different from that of a

Hi! If I build a vector of some length (e.g. 4) from a vector of another length (e.g. 3) then I get tons of extractelement and insertelement instructions. since vectors of length 3 and 4 both map to an sse register it could be useful to introduce an instruction that changes the length of a vector, either truncating or extending by zero or undef values (whichever makes more sense). for lengths 3

> ... adding the ability to concat > strings with '+' would be a relatively simple addition (no pun intended) to > the code base I believe. With a lot of other languages supporting this kind > of concatenation, this is what surprised me most when first learning R. Wow! R has a lot of surprising features and I would have thought this would be quite a way down the list. How

On Sat, Oct 9, 2010 at 7:59 AM, Jochen Wilhelmy <j.wilhelmy at arcor.de> wrote: > Hi! > > I'd like to use llvm::cl as it seems quite easy to use, but there > currently seems to be > a major drawback: if I do -help then all options from all llvm libs that > I have included > are shown, but I just have an input file and output file to specify. I've always found

Gabor, Thanks much. Your solution is elegant. My overall scheme is to take present date, and check whether it is a weekend, if not, then create a string based on the date, to concatenate into a url link for download.file( ). The files I need to download have a part which is in the format: mmddyy. I am working to make myself a system to connect to exchanges, and download end of day files from

Hi, first time poster here. During my time using R, I have always found string concatenation to be (what I feel is) unnecessarily complicated by requiring the use of the paste() or similar commands. When searching for how to concatenate strings in R, several top search results show answers that say to write your own function or override the '+' operator. Sample code like the following

Just to clarify, primitive (C-level) generics do not support dispatch on basic classes (like character). This is for performance (no need to consider dispatch on non-objects) and for sanity (in general, redefining fundamental behaviors is dangerous). It is of course possible to define a "+" method with a signature containing a class not in the set of basic classes. On Tue, Jun 16, 2015

On Tue, Jun 16, 2015 at 8:24 PM, Herv? Pag?s <hpages at fredhutch.org> wrote: [...] > > If I was to override `+` to concatenate strings, I would make it stick > to the recycling scheme used by arithmetic and comparison operators > (which is the most sensible of all IMO). Yeah, I agree, paste's recycling rules are sometimes painful. This could be "fixed" with a nice

Hi! These warnings and errors might be interesting to you when compiling rev. 116572 of llvm and clang on windows: \llvm\utils\killthedoctor\system_error.h(260) : error C2065: 'EAFNOSUPPORT' : undeclared identifier and many similar errors regarding the system error constants. msdn says it's WSAEAFNOSUPPORT instead of EAFNOSUPPORT (prepend WSA... to all system error constants)