Displaying 20 results from an estimated 10000 matches similar to: "package.skeleton only exports the first 73 lines of code"
2020 Jun 06
3
Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
The Rcpp package and some related packages such as RcppArmadillo make use of
(local) wrappers around the utils::package.skeleton() function for creating
(basic yet functional) packages using Rcpp or RcppArmadillo. RStudio also
exposes this under the graphical menu as a nice way to construct a package.
But it seems that something changed quite recently in R. I looked into this a
little yesterday
2006 Jul 19
1
Skeleton output support in speexenc
Hi,
I just added skeleton meta data output support in speexenc. The option
is disabled by default and can be enabled using -k or --skeleton. I'm
using a very simple skeleton API for handling skeleton packet
generation which is contained in skeleton.h & skeleton.c.
Please check the patch and whether xine/mplayer/quicktime and other
players support the skeleton enabled speex file. At the
2014 Aug 22
2
Merging Ogg streams whilst updating the Skeleton?
Hi All
I'm currently trying to put together an ogg file with two theora streams,
a handful of audio streams (probably mixed vorbis and opus), and a
Skeleton stream that describes their relationships to each other. I had
hoped to be able to use the oggz suite of tools, but I can't seem to get
that to work.
To generate my theora files, I'm using ffmpeg2theora, which will happily
2020 Jun 06
2
Change in package.skeleton behavior from R 3.6.3 to R 4.0.0 ?
On 06/06/2020 3:44 p.m., Duncan Murdoch wrote:
> On 06/06/2020 3:06 p.m., Dirk Eddelbuettel wrote:
... [deletions]
>> In short, 4.0.0 no longer exports via 'exportPattern("^[[:alpha:]]+")'
>> rendering the new package created non-functional.
>>
>> Was this intentional, or is this a bug we can look into fixing for R 4.0.2 ?
>
> It's in the
2010 Apr 29
3
Ogg index and Skeleton 4.0
Hi everybody,
I've updated OggIndex to now output Skeleton 4.0 tracks. The differences
between Skeleton 3.x and Skeleton 4.0 with OggIndex is:
* The fisbone packet now includes a "Radix" field.
* The fisbone packet now includes two new compulsory message
headers; "Role" and "Name".
* The fishead packet no longer includes "start time"
2013 Apr 14
1
Empty package skeleton
Hi,
I know this has been reported/asked before (
http://tolstoy.newcastle.edu.au/R/e15/devel/11/10/0831.html) but it would
still be just nice to have a fix for the not user-friendly fact that one
cannot create a completely empty package skeleton (see previous post for a
suggested patch).
In the same vein, I would add to the original suggestion from Herve Pages
that it would be nice to have a
2011 Jun 09
1
package.skeleton() does not create 'data' folder
Hi again, yesterday I mailed this query however I could not see this
on the mail list. Therefore, I am reposting it again.
I was using package.skeleton() function to create the
skeleton of my package in windows. Here is my attempt:
rm(list = ls())
setwd("F:/R_PackageBuild")
package.skeleton("trial1", namespace = TRUE, code_files =
"F:/R_PackageBuild/trial.r")
In
2008 Jul 15
1
package.skeleton does invalide regular name...
Hi the list,
I am using package.skeleton on a file that has a very classic name, but
package.skeleton detect it as a invalid name :
--- 8< -------
package.skeleton(name="packClassicBis",code_files="./packClassic/R/progClassic.R")
Cr?ation des r?pertoires...
Cr?ation de DESCRIPTION...
Cr?ation de 'Read-and-delete-me'...
Recopiage des fichiers de code...
Cr?ation
2011 Oct 14
1
Creating a package skeleton with no flesh
Hi,
Wouldn't it be awesome if package.skeleton() could be used to
produce, well... a package skeleton? In a fresh R session:
> package.skeleton("mypkg")
Error in !have : invalid argument type
This (not very informative) error message seems to occur because
I'm trying to create a skeleton with no flesh on it:
> foo <- function() {}
>
2008 Aug 07
1
package.skeleton does invalide regular name, bis... (PR#12020)
Hi the list,
I guess I find an other bug (the first one is at the end off this mail)
in package.skeleton. It occurs when we give as code_file some file that
are not in the current directories.
If we give a single file to code_file (like code_file=3D"riri/fifi.R"),
it does not reconize fifi.R as a regular name and change it to
riri/zfifi.R
If we give several file to code_file (like
2006 Aug 02
1
[PATCH] skeleton support for speexenc and speexdec
Hi,
I have done some code cleanup of my speexenc patch for skeleton
support. Also a warning message have been added to let the users know
that some decoders may fail with skeleton output enabled.
The speexdec patch enables speexdec to play skeleton enabled speex file.
Thanks in advance for the feedbacks.
--tahseen
-------------- next part --------------
A non-text attachment was scrubbed...
2008 Apr 13
1
R 2.7 package.skeleton
Hi the devel list
I am testing package.skeleton in R 2.7 (download today). I get an error
that I do not understand. I guess it is not an error from my code since
I have no probleme when I source it. So is it a error in
package.skeleton?
Here is my code :
--- 8< ------ File essai.r -------------
setClass(
Class="ClusterizLongData",
representation=representation(
2011 Oct 04
1
package.skeleton generates ".env = <environment>"
Hello,
i trying to create a package using package.skeleton. I use R.oo package to
create oriented-object classes. When i use package.skeleton, this creates
the following file:
classA <-
structure(function()
{
extend(Object(),"Class A",
.var1= NULL)
}
, .env = <environment>, class
2009 May 04
5
Convert skeleton to "regular" format
Hi there,
we just encountered a problem with some tools obviously encoding into
the skeleton format by default, which leads to problems with several
other tools, in that particular case it's oggCut. When we try to
edit/cut an ogg file with it, the program crashes with a segfault.
I was able to locate and fix the problem in the oggCut source but I am
wondering how to convert my ogg files to a
2008 Feb 12
2
[PATCH] skeleton.c
> Can you commit it in ffmpeg2theora? I think that and Speex are the
> only other places where skeleton.c is used, and ffmpeg2theora is
> likely to have Skeleton being used by default in the next release.
Then maybe it would be a good idea to do the API change needed for
checking magic now ?
2006 Mar 10
1
oggfile, skeleton and vorbis tools
----- Original Message -----
From: "Ian Malone" <ibmalone@gmail.com>
To: "ogg-dev" <ogg-dev@xiph.org>
Sent: Friday, March 10, 2006 5:24 PM
Subject: Re: [ogg-dev] oggfile, skeleton and vorbis tools
>> This is something we might want to extend skeleton to support, i know
>> we've talked about this kind of thing before. So that skeleton can
2014 Aug 23
2
Merging Ogg streams whilst updating the Skeleton?
On Sat, 23 Aug 2014, Silvia Pfeiffer wrote:
> What does oggz-info tell you about the file when you've merged it
> (without skeleton)? It may say that there are two logical video
> bitstreams, because they've come from different files. So, two
> skeletons may actually be correct.
There should be (and are) two logical video streams - I'm trying to create
a file with a
2006 Sep 12
1
package.skeleton() in R-2.4.1
Hi
R version 2.4.0 alpha (2006-09-06 r39158)
MacOSX 10.4.7
There was a thread some time ago as to whether the structure created by
package.skeleton() would pass R CMD check.
I have an example where package.skeleton() gives an R file that gives an
error when sourced.
If I type
setClass("brob",
representation = representation
2010 Jun 01
2
Fwd: Skeleton 4.0 draft, help with Dirac fields please!
On Tue, Jun 1, 2010 at 12:56 PM, Monty Montgomery <monty at xiph.org> wrote:
> On Mon, May 31, 2010 at 10:51 PM, Timothy B. Terriberry
> <tterribe at email.unc.edu> wrote:
>> Chris Pearce wrote:
>>> ? Hi Guys & Gals,
>>>
>>> I need you guys to decide whether we want to include extra granulepos
>>> fields to Skeleton 4. Given the
2005 Aug 31
1
Why should package.skeleton() fail R CMD check?
I find it a bit peculiar that a package skeleton created with a utils
function package.skeleton() fails subsequent R CMD check. I do
understand that the function is intended to produce only a skeleton that
should be edited by the package author. I think that it would be
justified to say that the skeleton *should* fail the test. However, I
have two arguments against intentional failure:
* When you