Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Standalone compiler"
2007 Feb 19
1
Documenting options specific to a package.
If one specifies new options in a package, using the options()
function, where does/should one document these new options?
E.g. suppose that I put the line
options(melvin=42)
in a file zzz.R in the R directory of the package source, where the
package contains functions foo(), bar(), clyde(), and irving() which
all query options("melvin") and take some action based on the value
of
2002 Apr 11
2
Obtaining names of ``...'' arguments.
This may be an FAQ, but a (perfunctory) search failed to turn it up.
Suppose I have a function foo(...){<something>} and I want to obtain,
inside foo, the names of items comprising the ``...''. E.g. if I
call
foo(melvin,clyde,irving)
I want to be able to loop through the ``...'' and successively obtain
the text strings "melvin", "clyde", and
2019 Nov 04
3
Puzzled about a new method for "[".
On 5/11/19 3:41 AM, Hadley Wickham wrote:
> For what it's worth, I don't think this strategy can work in general,
> because a class might have attributes that depend on its data/contents
> (e.g. https://vctrs.r-lib.org/articles/s3-vector.html#cached-sum). I
> don't think these are particularly common in practice, but it's
> dangerous to assume that you can restore a
2019 Nov 04
3
Puzzled about a new method for "[".
On 04/11/2019 4:40 p.m., Pages, Herve wrote:
> Hi Rolf,
>
> On 11/4/19 12:28, Rolf Turner wrote:
>>
>> On 5/11/19 3:41 AM, Hadley Wickham wrote:
>>
>>> For what it's worth, I don't think this strategy can work in general,
>>> because a class might have attributes that depend on its data/contents
>>> (e.g.
>>>
2006 Apr 13
4
Creating an environment for a function.
I am trying to build a function in a context where the environment
concept would appear to be useful. But I'm a bit foggy about this
concept and would appreciate some pointers and advice.
Basically the function I'm building, say foo(x,t), is a function of
two variables). Depending on the value of t, foo will return one of
the values f1(x), f2(x), ..., fk(x), where each of f1, ..., fk is
2001 Dec 20
2
library()
I've just installed version 1.4.0 of R, and am experiencing
a puzzling phenomenon with the library() function.
I have .lib.loc set as follows:
> .lib.loc
[1] "/usr/local/lib/R/library" "/home/faculty/rolf/Rlib"
If I invoke
> library(melvin)
I get the error message
Error in library(melvin) : There is no package called `melvin'
but if I invoke
>
2001 Nov 15
1
samba daemon won't start.
-----Original Message-----
From: MAKRO BAGAFORO, Melvin
Sent: Friday, November 16, 2001 11:52 AM
To: 'Ben Elliston'
Subject: RE: samba error
Hi Guys,
I already downloaded the latest config.guess
and config.sub files, './configure' command is now error free. However, I
have another problem, samba won't start. Samba test results:
2004 Dec 04
9
Excel *.xls files, RODBC
I gather from reading the back-issues of r-help that it should be
possible (modulo a number of caveats) to read an excel (yuck!) file
into R using RODBC. I have obtained and installed ODBC and the RODBC
package, but cannot for the life of me figure out how to go about
it. Can anyone give me a simple recipe?
I have an excel file on cdrom, say:
/mnt/cdrom/melvin.xls
I have started R and loaded
2002 Apr 12
1
Parrot
This is just an idea for comment. Perl6, the upcoming version of Perl has
separated out the runtime into a virtual machine called Parrot. There are
already several small languages (one is C-like, one is Java-like and one is
BASIC-like) that target Parrot and given the popularity of Perl its likely that
others may attempt to target it too.
If R could interface easily with Parrot then it might be
2015 Jan 31
2
Start up script fails
On 1/31/15, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 31, 2015, at 9:17 AM, Melvin Call <melvincall979 at gmail.com> wrote:
>
>> There is no other information provided, and there is nothing in the log to
>> help
>> either. Can anyone tell me what I need to do to make this output some
>> useful
>> information that I can use to further
2004 Sep 15
2
Slightly off-topic --- distribution name.
I've built R functions to ``effect'' a particular distribution, and
would like to find out if that distribution is already ``known'' by
an existing name. (I.e. suppose it were called the ``Melvin''
distribution --- I've built dmelvin, pmelvin, qmelvin, and rmelvin as
it were, but I need a real name to substitute for melvin.)
The distribution is really just a toy
2001 Nov 01
1
migration to common runtime?
I'm curious if any of the core R developers have considered the
possibility of hosting R (v2?) on the parrot common runtime environment.
Perl6 will generate byte-code for parrot, as will some future version of
python. I can imagine both drawbacks and advantages. Some advantages
would be fast byte-code execution and freely mixing perl, python and R
modules. Anyone looked into this?
Tim
2012 Apr 19
1
[LLVMdev] PBQP & CalcSpillWeights
Hi Arnaud,
I'm glad to hear that your test case is working.
I however still get my wrong allocation in some non trivial cases : the
> pairing constraint is not fulfilled.
>
> I have tried to modify the 'ensure pairable' pass (the pass undoing some
> of the coalescer's work) to always insert register copies for
> instructions with the pairable constraint, instead of
2001 Nov 18
2
log.smbd error -
Hi Everybody,
I keep getting this error from log.smbd:
find_name_on_subnet: on subnet 192.1.8.1 - name STORE 8<1d> NOT FOUND
I'm wondering where it is getting the name 'STORE 8', when my hostname is
'store8' (no space in-between).
Previously, I used 'store 8' as workgroup in smb.conf but I've already
changed it other names.
Do you have any idea what
2015 Feb 01
2
Start up script fails [/etc/killpower]
On 1/31/15, Charles Lepple <clepple at gmail.com> wrote:
> On Jan 31, 2015, at 3:09 PM, Melvin Call <melvincall979 at gmail.com> wrote:
>
>> One last question if you don't mind. I noticed the "default" POWERDOWNFLAG)
>> is
>> set to /etc/killpower, but I changed that to /tmp and modified my
>> umountroot
>> script to mount it read only
2015 Jan 31
0
Error: Connection failure: Connection refused
On Jan 30, 2015, at 4:22 PM, Melvin Call <melvincall979 at gmail.com> wrote:
> At this point I unplugged the UPS and plugged it into a different USP port, but
> that did not change the above. Figuring this was likely a udev problem, I
> created the following /etc/udev/rules.d/52-nut-usbups.rules (based on an example
> on our database server, and changing the vendor and product
2012 Apr 05
2
[LLVMdev] PBQP & CalcSpillWeights
Hi Lang,
Thanks a lot for taking time to look into this. I will test the fix soon and
let you know the results.
Cheers,
--
Arnaud de Grandmaison
On Tuesday, April 03, 2012 17:30:33 Lang Hames wrote:
> Hi Arnaud,
>
> Apologies for the delayed reply.
>
> Thank you for the excellent test case - it exposed a subtle bug in the
> colorability heuristic. This has been fixed in
2002 Apr 04
1
PR#1132.
Just now I again had occasion to want nested describe lists in a
documentation file. I found that the bug which I reported on 18
October, 2001 still persists. I checked on the bug report at the R
web page, and found that the notes say ``Not a problem in R 1.4.0
(2001-12-08)''.
Well, it's still a problem for me --- using R 1.4.1.
(Details:
platform sparc-sun-solaris2.7
arch
2012 Apr 03
0
[LLVMdev] PBQP & CalcSpillWeights
Hi Arnaud,
Apologies for the delayed reply.
Thank you for the excellent test case - it exposed a subtle bug in the
colorability heuristic. This has been fixed in r153958.
In case you are curious, the bug was as follows: the PBQP solver applies
applies a simplification step to each matrix. When all elements of a matrix
row or column are equal, the value for those elements is "pushed
2012 Apr 11
0
[LLVMdev] PBQP & CalcSpillWeights
Hi Lang,
The assert is not triggered any longer on my testcases :)
I however still get my wrong allocation in some non trivial cases : the
pairing constraint is not fulfilled.
I have tried to modify the 'ensure pairable' pass (the pass undoing some
of the coalescer's work) to always insert register copies for
instructions with the pairable constraint, instead of being smart and