What was misplaced about this?
By the way, we're at a point now where changes to the OOPHM branch need to
be reviewed.
On Mon, Sep 8, 2008 at 7:56 PM, <[EMAIL PROTECTED]> wrote:
>
> Author: [EMAIL PROTECTED]
> Date: Mon Sep 8 16:56:02 2008
> New Revision: 3633
>
> Modified:
>
>
> changes/jat/oop
On Tue, Sep 9, 2008 at 10:11 AM, Scott Blum <[EMAIL PROTECTED]> wrote:
> What was misplaced about this?
> By the way, we're at a point now where changes to the OOPHM branch need to
> be reviewed.
@John, are getting this working in your branch with the intent to
merge it into /branches/oophm later
On Tue, Sep 9, 2008 at 1:12 PM, BobV <[EMAIL PROTECTED]> wrote:
>
> On Tue, Sep 9, 2008 at 10:11 AM, Scott Blum <[EMAIL PROTECTED]> wrote:
> > What was misplaced about this?
> > By the way, we're at a point now where changes to the OOPHM branch need
> to
> > be reviewed.
>
> @John, are getting thi
On Tue, Sep 9, 2008 at 1:11 PM, Scott Blum <[EMAIL PROTECTED]> wrote:
> What was misplaced about this?
>
The break needs to happen if a plugin was successfully found rather than if
an error occurred trying to initialize it.
> By the way, we're at a point now where changes to the OOPHM branch ne
On Tue, Sep 9, 2008 at 1:24 PM, John Tamplin <[EMAIL PROTECTED]> wrote:
> On Tue, Sep 9, 2008 at 1:11 PM, Scott Blum <[EMAIL PROTECTED]> wrote:
>
>> What was misplaced about this?
>>
>
> The break needs to happen if a plugin was successfully found rather than if
> an error occurred trying to initi
On Tue, Sep 9, 2008 at 1:28 PM, Scott Blum <[EMAIL PROTECTED]> wrote:
> I don't understand. If a plugin was found but failed to connect, and we
> call the module load error function, why would we continue iterating through
> the list? Once you've found a plugin that loads, that's the right plugi
