Perl Development

I am posting this to the list in order to better determine the
direction of SDLpl development. I see SDLpl as a useful tool
to quickly mock up larger projects, and as a scripting engine
which can be embedded in SDL applications.

That said, if you are someone who would use perl to write a
game / web browser / etc. Would you be more or less inclined
to write the entire thing in perl:

1.) If you had access to pre-fab rendering engines 2d scroller, 3d flight. etc
2.) If there was an object orient interface (beyond the pure fuctional)
3.) If there was a perl interpreter with SDL built in?

Also on the flip side, would you be more or less inclined to use
perl with another language C/C++ if:

1.) A simplified interface to the perl interpreter was included
2.) If a step by step tutorial on using XS with SDL were available
3.) Perl’s internals stopped sucking, and the Inline::C module
worked far more often?

If you want to look at the current stable release, or the first pre-release
of the SDL 1.2 compliant series visit http://sdlpl.sourceforge.net.

I’d really appreciate the insight of people who use the PyGame package
as well. What features of PyGame are really nice, and should be
available across all languages?–

david j. goehrig bit twiddler www.valinux.com
cf. www.tuxedo.org/~esr/jargon/html/entry/bit-twiddling.html 31337157 508

I am posting this to the list in order to better determine the
direction of SDLpl development. I see SDLpl as a useful tool
to quickly mock up larger projects, and as a scripting engine
which can be embedded in SDL applications.

That said, if you are someone who would use perl to write a
game / web browser / etc. Would you be more or less inclined
to write the entire thing in perl:

1.) If you had access to pre-fab rendering engines 2d scroller, 3d flight. etc

2D scrollers are always nice… But they can make programmer’s lazy :wink:

2.) If there was an object orient interface (beyond the pure fuctional)

I would like that for SDLpl. In C/C++, I still prefer normal C over C++ (no
flames, just an opinion!), but for Perl (and Python and others) I do prefer the
OO approach over procedural.

Plus, keeping SDLpl OO will keep it more like the majority of other Perl
modules.

3.) If there was a perl interpreter with SDL built in?

That would be something … perhaps not the most practical for many other
things… but it would certainly be right up the alley of an educational
project I have been kicking around (conceptually) for a year now.

Also on the flip side, would you be more or less inclined to use
perl with another language C/C++ if:

1.) A simplified interface to the perl interpreter was included

Nice, but I suspect very hard and probably beyond your SDLpl’s scope.

2.) If a step by step tutorial on using XS with SDL were available
3.) Perl’s internals stopped sucking, and the Inline::C module
worked far more often?

Again… see above ;-)On Thu, 15 Mar 2001, you wrote:


Sam “Criswell” Hart <@Sam_Hart> AIM, Yahoo!:
Homepage: < http://www.geekcomix.com/snh/ >
PGP Info: < http://www.geekcomix.com/snh/contact/ >
Advogato: < http://advogato.org/person/criswell/ >

I am posting this to the list in order to better determine the
direction of SDLpl development. I see SDLpl as a useful tool
to quickly mock up larger projects, and as a scripting engine
which can be embedded in SDL applications.

That said, if you are someone who would use perl to write a
game / web browser / etc. Would you be more or less inclined
to write the entire thing in perl:

1.) If you had access to pre-fab rendering engines 2d scroller, 3d flight.
etc

Yes, definitely. The power of scripting languages is the high level stuff,
while the low level stuff could use the speed of C or C++.

2.) If there was an object orient interface (beyond the pure fuctional)

Naah… You know what I think about OO. :wink:

3.) If there was a perl interpreter with SDL built in?

Well, if that means it becomes truly portable to all or most SDL target
platforms; definitely yes! Portability without the issues with compilers,
libs etc, is one of the major advantages of scripting languages. (And VM
based solutions like Java, of course.)

Also on the flip side, would you be more or less inclined to use
perl with another language C/C++ if:

1.) A simplified interface to the perl interpreter was included

I guess so, although I don’t know what it looks like now.

2.) If a step by step tutorial on using XS with SDL were available

Probably - I’m having trouble keeping all mini-projects going as it is,
without being forced to dig into massive reference manuals and the like to
learn new stuff. :slight_smile:

3.) Perl’s internals stopped sucking, and the Inline::C module
worked far more often?

I don’t think I know enough about those to comment. :slight_smile:

//David

.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------> http://www.linuxaudiodev.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |--------------------------------------> david at linuxdj.com -'On Thursday 15 March 2001 17:28, Dave wrote:

Can anyone help me out with this error message:
xmps: error in loading shared
libraries: /usr/local/lib/xmps/renderers/video/libsdl.so: undefined
symbol: SDL_QuitSubSystem

I get it whenever I try to play a video with xmps (a mpeg player that uses
sdl) I tried their list and they told me to write here.

thanks,

eli

the heathen sadistic-ritualistic mass-mutterer

Can anyone help me out with this error message:
xmps: error in loading shared
libraries: /usr/local/lib/xmps/renderers/video/libsdl.so: undefined
symbol: SDL_QuitSubSystem

Try uninstalling xmps and reinstalling the latest version.
You have libraries from two different versions here.

See ya,
-Sam Lantinga, Lead Programmer, Loki Entertainment Software

Actually (not to cause any flame-wars or anything :wink: but the OO interface can
keep it more inline with the existing Perl modules… making it accepted easier
for more Perl developers.On Thu, 15 Mar 2001, you wrote:

On Thursday 15 March 2001 17:28, Dave wrote:

2.) If there was an object orient interface (beyond the pure fuctional)

Naah… You know what I think about OO. :wink:


Sam “Criswell” Hart <@Sam_Hart> AIM, Yahoo!:
Homepage: < http://www.geekcomix.com/snh/ >
PGP Info: < http://www.geekcomix.com/snh/contact/ >
Advogato: < http://advogato.org/person/criswell/ >

Yes, that’s nice, of course.

(I’m not really against OO; only some of the stuff that "standard"
C++ style OO brings in with it. And that’s an entirely different
discussion that’s not related to Perl nor SDL. :slight_smile:

//David

.- M A I A -------------------------------------------------.
| Multimedia Application Integration Architecture |
| A Free/Open Source Plugin API for Professional Multimedia |
----------------------> http://www.linuxaudiodev.com/maia -' .- David Olofson -------------------------------------------. | Audio Hacker - Open Source Advocate - Singer - Songwriter |--------------------------------------> david at linuxdj.com -'On Saturday 17 March 2001 06:25, Samuel Hart wrote:

On Thu, 15 Mar 2001, you wrote:

On Thursday 15 March 2001 17:28, Dave wrote:

2.) If there was an object orient interface (beyond the pure
fuctional)

Naah… You know what I think about OO. :wink:

Actually (not to cause any flame-wars or anything :wink: but the OO
interface can keep it more inline with the existing Perl modules…
making it accepted easier for more Perl developers.