<div class="blog">
<h1 id="NAME">
-Frozen Bubble coming to CPAN
+The beginnings of modular design for SDL Perl
</h1>
<div class="CONTENT">
-<div style="text-align: right;"><i>The frozen wind,</i></div><div style="text-align: right;"><i> made me shiver,</i></div><div style="text-align: right;"><i> with excitement</i>.</div><div style="text-align: right;"></div><br /><div style="text-align: left;">There has been some interest in making Frozen Bubble cross platform so I have forked Frozen Bubble v2.0 to my github<a href="http://github.com/kthakore/frozen-bubble/tree/master"> repo</a>. Any contributors are welcome! I will eventually be removing hacks that were needed to make Frozen Bubble work with the old SDL perl. The plan is to make Frozen Bubble cross platform by removing platform specific hacks and dependencies. One of the major switch will be from BSD sockets to SDL_net through SDL perl or XS. The main goal would be to be able to do </div><div style="text-align: left;"></div><blockquote><div style="text-align: left;">cpan install FrozenBubble</div></blockquote><div style="text-align: left;"></div><div style="text-align: left;">To do this the Makefile.PL will need to be rewritten a little bit. Moreover we will need to make test using code from Frozen Bubble so that it can be smoke tested on CPAN. If contributors need more information please contact me.</div><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-4948555691607200165?l=yapgh.blogspot.com'/></div></div>
\ No newline at end of file
+<div style="text-align: right;"><i>“Do or do not... there is no try.”</i><br /></div><div style="text-align: right;"><i>--yoda </i><br /><br /></div><h1>The design before</h1><br />The bindings before were all in <a href="http://github.com/kthakore/SDL_perl/blob/master/src/SDL.xs">one huge XS file</a>. This was then exported into the SDL module. This means that the XS file has to handle with macros if any component (e.x SDL_Mixer) is not compiled. Moreover having ever binding in one XS file prevents use to treat C structs as object with only one point of free and malloc. This would be BEGIN and DESTROY in Perl. Also the monolithic design introduces a lot of bugs because we have to use free and malloc all over the place. Lastly SDL monolithic design has the constructor for all structs in both Perl and in XS. <br /><br /><h1>The design we are aiming for</h1>Simple <a href="http://github.com/kthakore/SDL_perl/blob/master/src/Rect.xs">one XS</a> per Module. This would also simplify the Build code.<br /><br /><h2>First Step </h2><br />We have began with SDL Rect. It is in github master branch now. We are in the progress of making it back compatible. Originally SDL::Rect took named variables as parameters for new(). Now since the constructor <a href="http://github.com/kthakore/SDL_perl/blob/master/src/Rect.xs#L16">is in XS</a> we have only unnamed parameters. <br /><br /><br /><h3>Before</h3><br />SDL::Rect->new( -x => 0, -y => 0, -width => 0, -height => 0);<br /><br /><h3>After</h3><br />SDL::Rect->new(0, 0, 0, 0);<br /><br />Ideally we would like both ways of constructing Rect.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-6151839795039915111?l=yapgh.blogspot.com' alt='' /></div></div></div>
\ No newline at end of file
projects / sdlgit/SDL-Site.git / blobdiff