On Thu, Nov 30, 2000 at 05:07:32AM +0000, David Grove wrote:
> >From my understanding, "API" is the set of functions internal to Perl and
> PerlXS that allow C to access Perl internal structures, functions, etc.,
> for the purpose (or effect) of "writing" "Perl" in "C" (SvPV(whatsis)).
Uhm, no. An API is a *programming interface*. It tells you what functions are
available. That's all. It's the reference manual to a library. It's a way of
handing a programmer a black box; you don't need to care how the functions are
implemented, you're just told what they are and what they do. You can't write
anything "in API". You can write an API, or you can use an API.
> Dan: In any PDD generated from this group, we really need to define for
> the "semantically challenged" the terms that are used within it
You know why we have a reading list, right? It's so you can read books which
explain these things for you; this means that *WE DON'T HAVE TO*.
I categorically do *NOT* want perl6-internals to turn into a basic course in
compiler design, purely for the benefit of those who know nothing at all about
what they're trying to achieve. I'd like Perl 6 to be a masterwork, and
masterworks require master craftsmen. If you want to partake in compiler
design, it makes more than a little sense to find out how to do so.
--
\let\l\let\l\d\def\l\a\active\l~\catcode~`?\a~`;\a\d;{~`};!\a\d!{?;~}\l?\the;#
!;]!\l]\l;\.!;,!;\%!;=!]=\d],\expandafter;[!][{=%{\message[};\$!=${\uccode`'.
\uppercase{,=,%,{%'}}};*!=*{\advance.by}]#\number;/!=/{*-1}\newcount.=\-{*-};-
!]-\-;^!=^{*1};\ != {.`\ $};@!=@{,.,"#`@^$}.`#*`'$.!0-!$//$^$ .``^$*!$^$.!0-!/
$!-!^$@*!$ *!*!*!*!$@-!$ .!0-!-!$.``^$^^$.`<-!*`<$@*!$%}\batchmode
