Maintainer: ‘Telford Tendys <gafit@lnx-bsp.net>’

No Authors@R field in DESCRIPTION.
Please add one, modifying
  Authors@R: person(given = "Telford",
                    family = "Tendys",
                    role = c("aut", "cre"),
                    email = "gafit@lnx-bsp.net")
as necessary.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’
These entry points may be removed soon:
‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
Maintainer: ‘Telford Tendys <gafit@lnx-bsp.net>’

No Authors@R field in DESCRIPTION.
Please add one, modifying
  Authors@R: person(given = "Telford",
                    family = "Tendys",
                    role = c("aut", "cre"),
                    email = "gafit@lnx-bsp.net")
as necessary.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’
These entry points may be removed soon:
‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’
File ‘gafit/libs/gafit.so’:
  Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
These entry points may be removed soon:
‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’
File ‘gafit/libs/gafit.so’:
  Found no calls to: ‘R_registerRoutines’, ‘R_useDynamicSymbols’
These entry points may be removed soon:
‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.
It is good practice to register native routines and to disable symbol
search.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File 'gafit/libs/x64/gafit.dll':
  Found non-API calls to R: 'FRAME', 'HASHTAB'
These entry points may be removed soon:
'FRAME', 'HASHTAB'

Compiled code should not call non-API entry points in R.

See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File ‘gafit/libs/gafit.so’:
  Found non-API calls to R: ‘FRAME’, ‘HASHTAB’

Compiled code should not call non-API entry points in R.

See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual,
and section ‘Moving into C API compliance’ for issues with the use of
non-API entry points.
File 'gafit/libs/x64/gafit.dll':
  Found non-API calls to R: 'FRAME', 'HASHTAB'

Compiled code should not call non-API entry points in R.

See 'Writing portable packages' in the 'Writing R Extensions' manual,
and section 'Moving into C API compliance' for issues with the use of
non-API entry points.