Affix
view release on metacpan or search on metacpan
Affix.
```
BEGIN{ $Affix::VMSize = 2 ** 16; }
```
This value is `4096` by default.
# Examples
The best example of use might be [LibUI](https://metacpan.org/pod/LibUI). Brief examples will be found in
`eg/`. Very short examples might find their way here.
# See Also
All the heavy lifting is done by [dyncall](https://dyncall.org/).
Check out [FFI::Platypus](https://metacpan.org/pod/FFI%3A%3APlatypus) for a more robust and mature FFI
[LibUI](https://metacpan.org/pod/LibUI) for a larger demo project based on Affix
dyncall/doc/manual/callconvs/callconv_x86.tex view on Meta::CPAN
% \hhline{~-~~}
% & \vdots & & \\
% \end{tabular}
% \caption{Stack layout on x86 thiscall (GNU) calling convention}
% \end{figure}
\subsubsection{pascal}
The best known uses of the pascal calling convention are the 16 bit OS/2 APIs, Microsoft Windows 3.x and Borland Delphi 1.x.
It is a variation of stdcall, however, arguments are passed from left-to-right.
Since this calling convention is for 16-bit APIs, it is not discussed in
further detail, here.
\subsubsection{plan9call}
\paragraph{Registers and register usage}
lib/Affix.pm view on Meta::CPAN
You may control the max size of the internal stack that will be allocated and
used to bind the arguments to by setting the C<$VMSize> variable before using
Affix.
BEGIN{ $Affix::VMSize = 2 ** 16; }
This value is C<4096> by default.
=head1 Examples
The best example of use might be L<LibUI>. Brief examples will be found in
C<eg/>. Very short examples might find their way here.
=head1 See Also
All the heavy lifting is done by L<dyncall|https://dyncall.org/>.
Check out L<FFI::Platypus> for a more robust and mature FFI
L<LibUI> for a larger demo project based on Affix
( run in 1.244 second using v1.01-cache-2.11-cpan-4e96b696675 )