# Robert Penners programming FMX book

**URL:** <https://forum.kirupa.com/t/robert-penners-programming-fmx-book/93957>\
**Category:** Uncategorized\
**Created:** [November 6, 2003, 6:55pm UTC](https://forum.kirupa.com/t/robert-penners-programming-fmx-book/93957 "2003-11-06T18:55:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![APDesign](https://avatars.discourse-cdn.com/v4/letter/a/e47c2d/32.png) [@APDesign](https://forum.kirupa.com/u/APDesign)\
**Post date:** [November 6, 2003, 6:55pm UTC](https://forum.kirupa.com/t/robert-penners-programming-fmx-book/93957/1 "2003-11-06T18:55:28Z")

</div>

Hey, I just picked up this book because of all the great stuff I’ve heard about it, and I was wondering if there is anything in here that would be considered “bad practice” now with Flash MX 2004 being out. In chapter 2 it goes over a lot of Object Oriented programming techniques which include things like **constructor** and his custom ways of finding the **constructor** , as well as the use of **proto** instead of new. Also his extend(); function

```auto

Function.prototype.extend(superclass){
this.prototype. __proto__ = superclass.prototype;
this.prototype. __constructor__ = superclass;
}

```

and superCon(); funciton

```auto

Child.prototype.superCon = function(){
  arguments .caller.prototype. __proto__.constructor.apply(this,arguments);
}

```

were two that worried me a little as far as “am I learning outdated stuff that will just confuse me when it no longer works” (which I hate being victim to)

Any comments or suggestions as far as what to ignore/do “better” would be appreciated.