<div class="blog">
<h1 id="NAME">
-Why I will be sticking to CPAN
+The beginnings of modular design for SDL Perl
</h1>
<div class="CONTENT">
-<div style="text-align: right;"><i>sculpted in clay,</i></div><div style="text-align: right;"><i>then fired to glass.<br /></i><i><br /></i></div><br />Recently there was really long <a href="http://www.nntp.perl.org/group/perl.sdl.devel/2009/09/msg1424.html">discussion </a>on sdl-devel@perl.org about providing packages for SDL perl rather than focusing on CPAN releases. The gists of the argument was that SDL perl should be making platform specific packages for end users. I agree with this idea but I do have to face the truth. <br /><br />The truth is there are very few developers currently working on SDL Perl. The truth is CPAN provides several tools that which currently drives development for SDL Perl. There are people interested in packaging SDL Perl (<a href="http://rt.cpan.org/Ticket/Display.html?id=49003">kmx</a>, <a href="http://www.nntp.perl.org/group/perl.sdl.devel/2009/09/msg1433.html">jean</a> and Jerome Quelin). The truth is there are other very <a href="http://rt.cpan.org/Ticket/Display.html?id=49084">critical areas</a> we can focus on. <br /><br />If there are people looking to package SDL Perl for their platform please contact us at sdl-devel@perl.org.<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/3102167581424744259-6565605958523853965?l=yapgh.blogspot.com'/></div></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>
+<p><a href="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/0/da"><img src="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/0/di" border="0" ismap="true"></img></a><br/>
+<a href="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/1/da"><img src="http://feedads.g.doubleclick.net/~a/kLUEuAPtuInPChqB2WfChUn3YyI/1/di" border="0" ismap="true"></img></a></p><img src="http://feeds.feedburner.com/~r/YetAnotherPerlGameHackeryapgh/~4/uEzoBWRJEks" height="1" width="1"/></div></div>
\ No newline at end of file
projects / sdlgit/SDL-Site.git / blobdiff