Aliasing of C functions in .CATS files

Google Group
1

What is the point in having aliasing of C functions in a .CATS file only to
have that aliasing unused in the corresponding .SATS file.

e.g.,

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

fun SDL_DestroyWindow (SDL_Window_ptr0): void = “mac#%”

I would think we’d want this as the second line:

fun SDL_DestroyWindow (SDL_Window_ptr0): void = "mac#
atscntrb_SDL2_SDL_DestroyWindow "

Which would seem to give some level of abstraction in case the C API
changes. If this is not the case, then I don’t understand the point in
having the first line:

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

2

The scope of ATS_EXTERN_PREFIX is the file in which it is defined.On Wednesday, February 5, 2014 10:56:02 AM UTC-5, Brandon Barker wrote:

Ah ok, but I now wonder what controls the scope of ATS_EXTERN_PREFIX,
since it seems it would be easy to have these overwrite each other as they
are currently defined (when using multiple libraries).

On Wednesday, February 5, 2014 10:43:27 AM UTC-5, gmhwxi wrote:

'mac#%" stands for “atscntrb_SDL2_SDL_DestroyWindow” in this case. This
is because the following declaration in SDL.sats:

#define ATS_EXTERN_PREFIX “atscntrb_SDL2_” // prefix for external names"

On Wednesday, February 5, 2014 9:54:39 AM UTC-5, Brandon Barker wrote:

What is the point in having aliasing of C functions in a .CATS file only
to have that aliasing unused in the corresponding .SATS file.

e.g.,

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

fun SDL_DestroyWindow (SDL_Window_ptr0): void = “mac#%”

I would think we’d want this as the second line:

fun SDL_DestroyWindow (SDL_Window_ptr0): void = "mac#
atscntrb_SDL2_SDL_DestroyWindow "

Which would seem to give some level of abstraction in case the C API
changes. If this is not the case, then I don’t understand the point in
having the first line:

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

3

Ah ok, but I now wonder what controls the scope of ATS_EXTERN_PREFIX, since
it seems it would be easy to have these overwrite each other as they are
currently defined (when using multiple libraries).On Wednesday, February 5, 2014 10:43:27 AM UTC-5, gmhwxi wrote:

'mac#%" stands for “atscntrb_SDL2_SDL_DestroyWindow” in this case. This
is because the following declaration in SDL.sats:

#define ATS_EXTERN_PREFIX “atscntrb_SDL2_” // prefix for external names"

On Wednesday, February 5, 2014 9:54:39 AM UTC-5, Brandon Barker wrote:

What is the point in having aliasing of C functions in a .CATS file only
to have that aliasing unused in the corresponding .SATS file.

e.g.,

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

fun SDL_DestroyWindow (SDL_Window_ptr0): void = “mac#%”

I would think we’d want this as the second line:

fun SDL_DestroyWindow (SDL_Window_ptr0): void = "mac#
atscntrb_SDL2_SDL_DestroyWindow "

Which would seem to give some level of abstraction in case the C API
changes. If this is not the case, then I don’t understand the point in
having the first line:

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

4

'mac#%" stands for “atscntrb_SDL2_SDL_DestroyWindow” in this case. This
is because the following declaration in SDL.sats:

#define ATS_EXTERN_PREFIX “atscntrb_SDL2_” // prefix for external names"On Wednesday, February 5, 2014 9:54:39 AM UTC-5, Brandon Barker wrote:

What is the point in having aliasing of C functions in a .CATS file only
to have that aliasing unused in the corresponding .SATS file.

e.g.,

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow

fun SDL_DestroyWindow (SDL_Window_ptr0): void = “mac#%”

I would think we’d want this as the second line:

fun SDL_DestroyWindow (SDL_Window_ptr0): void = "mac#
atscntrb_SDL2_SDL_DestroyWindow "

Which would seem to give some level of abstraction in case the C API
changes. If this is not the case, then I don’t understand the point in
having the first line:

#define atscntrb_SDL2_SDL_DestroyWindow SDL_DestroyWindow