Sorry for not being too quick on this XS thing, but I'm just confused on something.
Does this change mean the whole quest::say(), etc, system is gone and no longer usable?
And if so, what exactly, besides the general XS term, is replacing it? I've been looking into XS and what it is generally, and what I found was not too good on my part:
Quote:
Learning XS is very difficult, for two reasons.
The first is that the core Perl docs, such as perlxs and perlguts, tacitly assume that you already understand XS. Accordingly, they omit or gloss over crucial assumptions and background information. This sounds bad, but it is actually rather common in the Unix world.
The second is that you can't learn XS. Not as such. Not from the top down. This problem is much more profound than the first, and it stems not from any inadequacy in the documentation, but from what XS is -- and isn't.
The Perl docs refer to XS as a language, but it isn't. XS is a collection of macros. The XS langauge processor is a program called xsubpp, where pp is short for PreProcessor, and PreProcessor is a polite term for macro expander. xsubpp expands XS macros into the bits of C code necessary to connect the Perl interpreter to your C-language subroutines.
Because XS isn't a language, it lacks structure. The underlying C code has structure, but you can't see it, because it is hidden behind the macros. This makes it virtually impossible to learn XS on its own terms.
|
That's only one of the many things I've read about XS :(
And as a person who is struggling to learn C++ in the first place, does this mean everyone who is not fluent in that language can no longer write quests for their server?
I certainly hope this isn't the case, and if it is, then maybe someone who is XS savvy could guide us who aren't too quick on this on how to do basic functions?
This is just me voicing my opinion and concern on the matter, though, and I might just be confused. Any clearing up on this would be greatly appreciated. |