The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
wrassp 1.0.5
bug fixes
- adapted to CRAN’s compiler warnings
wrassp 1.0.4
bug fixes
- adapted to CRAN’s compiler warnings
wrassp 1.0.3
bug fixes
- adapted to CRAN’s compiler warnings
wrassp 1.0.2
bug fixes
- adapted to CRAN’s compiler warnings
- changed http links to https and support.rstudio.com to support.posit.co
wrassp 1.0.1
bug fixes
- type casting begin/end parameter values to numeric if they are integer values in
read.AsspDataObj()
(fixes IPS-LMU/emuR#231)
- checking max header size of SSFF files in putSSFFhdr and issuing warning instead of breaking the current R session. (closes #38)
wrassp 1.0.0
bug fixes
- fixed broken UTF-8 support on in windows paths
wrassp 0.1.9.9000
- replaced ms with (the correct) seconds in
read.AsspDataObj
function doc.
- implemented
as_tibble
S3 method for AsspDataObjects
bug fixes
- using return value of
fread
in labelobj.c
- removed
*(c++) == 0.0;
line that was causing [-Wunused-value] warning
wrassp 0.1.8
- exposing/using long instead of short windows function list
- added deprecation warning to the
wrassp_intro
vignette
bug fixes
wrassp 0.1.7
bug fixes
- fixed GCC >= 8.0 [-Wformat-overflow=] significant warning in numdecim.c
wrassp 0.1.6
bug fixes
- fixed rchk issues
- adressed comments by cran maintainer about description files
wrassp 0.1.5
bug fixes
- added explicit (void **) type casts for
get
and put
functions
- increased char array sizes for
sprintf
to combat compiler warnings of potential buffer overflow
wrassp 0.1.4
- added verbose parameter to sig. proc. functions
- added new package docs (?wrassp)
- updated wrassp_intro vignette to include ?wrassp reference
- improved documentation
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.