search for: exestr

Displaying 6 results from an estimated 6 matches for "exestr".

Did you mean: eest
2008 Jan 11
2
communicate from Rterm
...you all. ***************************** Public Sub Repo() ds = InputBox("Type in reporting date as YYYY-MM-DD", "reporting date") ''----- weird way to pass the date argument as Windows won't ''----- execute the command line directly, so I create a .bat exestr = "Rterm --restore --save --args " & ds & " < m.in.R > out.txt" Set fs = CreateObject("Scripting.FileSystemObject") Set a = fs.CreateTextFile("rpcd.bat", True) a.writeline (exestr) a.Close ret = Shell("rpcd.bat") MsgBox ("wait fo...
2008 Jan 18
0
more help needed Re: communicate from Rterm
...ther Windows runtimes may handle redirection themselves.) Compare the R-for-Windows system() and shell() commands and you will see one way to do this. On Fri, 11 Jan 2008, Duncan Murdoch wrote: > On 1/11/2008 10:14 AM, stephen bond wrote: >> I try with: >> >> ret = Shell(exestr) >> >> and it starts R, but the source file is not executed > > That's a VBA issue. VBA isn't handling the input redirection "< m. in.R > > out.txt". I don't know how to set that up: you'll need to contact > Microsoft tech support. > &g...
2013 Jan 16
2
[LLVMdev] RFC: auto-linking IR proposal
...tch > produces directives that work with Visual Studio 2010 using the > now-deprecated > dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: http://msdn.microsoft.com/en-us/library/7f0aews7.aspx only talks about the "exestr" comment type being deprecated. I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that means the dependent library feature is also deprecated. /* beginning of patch */ > > Index: /home/ygao/LLVM/llvm/lib/Target/X86/X86AsmPrinter.cpp &...
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
...produces directives that work with Visual Studio 2010 using the now-deprecated >> dependent library feature (commits r168779 and r168694). > Is that feature now-deprecated? The documentation here: > http://msdn.microsoft.com/en-us/library/7f0aews7.aspx > only talks about the "exestr" comment type being deprecated. > I see that the /defaultlib flag itself to the linker is deprecated, but it isn't clear to me that that means the dependent library feature is also deprecated. To clarify, at one point LLVM IR had a way to list dependent libraries in the form of deplibs...
2013 Jan 16
0
[LLVMdev] RFC: auto-linking IR proposal
Hi Daniel, Nice to meet you. My understanding of the Microsoft #pragma comment(lib, ...) semantics is that each specified library will be converted into a directive that starts with "/DEFAULTLIB" in the COFF .drectve section. To demonstrate, the following patch produces directives that work with Visual Studio 2010 using the now-deprecated dependent library feature (commits r168779 and
2013 Jan 15
4
[LLVMdev] RFC: auto-linking IR proposal
Hi all, We plan to add some auto-linking support for Mach-O, and need a scheme for encoding this information in the LLVM IR. We would like the same scheme to be able to support Microsoft's #pragma comment(lib,...) and #pragma comment(library, ...) features eventually. The current proposal is as follows: -- #1. Extend module-level metadata flags (llvm.module.flags) to support two new