onboardc-project — Main list for discussing needed features, fixes, and development strategies

[Onboardc-project] RE: [OnBC] Welcome aboard!

[Blake W. <bw...@la...>]

Do you mind if I pick your collective brains a little about the
concatenating string constants feature? 

I've added some code to the bottom of getNextToken (in OnBoardC.c)
which looks like this:

if (ps->token == DoubleQuote) {
	// If it's a DoubleQuote, let's scan for some more, and merge them.
	MemHandle h = MemHandleNew( 1 );
	Char *start = NULL;
	long value = 0;
	while (ps->token == DoubleQuote) {
		// Let's copy the data over...
		Err err = MemHandleResize( h, value + ps->value + 1 );
		if ( err != errNone ) {
			ps->token = Token_Error;
			return savePtr;
		}
		start = MemHandleLock( h );
		if ( start == NULL ) {
			ps->token = Token_Error;
			return savePtr;
		}
		MemMove( start + value, ps->start, ps->value + 1 );
		value += ps->value;
		savePtr = result;
		result = getNextLexeme(result, ps);
		err = MemHandleUnlock( h );
		if ( err != errNone ) {
			ps->token = Token_Error;
			return savePtr;
		}
	}
	ps->token = DoubleQuote;
	start = MemHandleLock( h );
	if ( start == NULL ) {
		ps->token = Token_Error;
		return savePtr;
	}
	ps->start = start;
	ps->value = value;
	result = savePtr;
}

So, basically, I create a new MemHandle, and concatenate all the
adjacent string values into it.  I did it this way because I really
think that we don't want to change the contents of ps->start, since
that that's the user's actual memo...

My problem now is that I can't free that memory in the getNextToken
block, because I need to pass it out, but the thing I'm passing it
to has no idea whether it needs to be freed or not.  (I guess, at
this point, we always need to free the memory for DoubleQuote tokens,
so I could make that change when we add the string constant.)

I guess I'm just wondering if you could give me a quick walkthrough of
what happens after I return a DoubleQuote token from getNextToken.
(It looks like it would eventually go to one of AddStringConstantNode
 or addStringConstant, but I'm not sure.)

The other thing I notice is that we add a lot of Nodes to the tree,
but I can't see where we pop them off again.

Thanks,
Blake.

[Onboardc-project] RE: [OnBoardC] prc-tools Porting Question.

[Blake W. <bw...@la...>]

> From: OnB...@ya... On Behalf Of Jerramy Gipson
> It's not particularly hard to get OnboardC to compile.  I'd 
> say you just signed yourself up! ;o)

Hmm, yes, easy.  Well, easy-ish.

Has anyone on this list successfully debugged OnBoardC using
CodeWarrior 9?  I can build it, and compile it, and get an error
where I expect an error, but I can't seem to set a breakpoint in
compile.c, round about like 3002.

Any suggestions would be appreciated.

Thanks,
Blake.

Re: [Onboardc-project] Defining Macros.

[Steve L. <ste...@gm...>]

On 9/6/05, Blake Winton <bw...@la...> wrote:
> But surely you see more of that than other open-source projects, what
> with all you users by definition knowing the language you used to write
> the code.  :)

True, but alot are relatively new to C programming, and compilers can
be a slightly intimidating area to play in...

> > I'd suggest removing the parens from the macro definition if no
> > arguments are intended.
>=20
> Well, yeah, I could do that, but I really want it to look like a
> function call.  (It's the "FAIL()" pseudo-method in the Test Framework.)

Fair enough. It's nice to be as compatible with other compilers as
possible, so fixing this is a good step in the right direction.

> > It would be nice to add these features. Could you add them as feature
> > requests on the sourceforge page, so we can keep track of them?
> > http://sourceforge.net/tracker/?atid=3D478289&group_id=3D55794
>=20
> I will, but I might take a crack at them before I do.

If you wouldn't mind, please add them even if you fix them. I also use
those trackers to list the changes/fixes/improvements made since the
last release, so it's nice to put things in, even if they get closed
straight away.

> > For the first one (concatenating string constants), take a look at
> > compile.c, ~line 3009. (Search for DoubleQuote), which is where quoted
> > strings are handled.
> >
> > For the # preprocessor operator, you probably need to look at the
> > macro argument expansion code, in OnBoardC.c (which you've already
> > looked at it seems...)
>=20
> Cool, I'll see what I can do in there, after I get it all set up.

Great, thanks! If you have any problems getting set up, let me know
and I'll try to help. Likewise if you have questions about the code
itself. I didn't write most of it, but I'm pretty familiar with it.

> > Again, we'd love to have you on the team, if you're interested in
> > helping out by contributing.
>=20
> I'm glad to submit patches when I can, but please don't put me on
> the team.  I'm already on six or seven teams that I only submitted
> a couple of patches to.  ;)
>=20
> Ah, what the hell.  Add me (I think I'm bwinton on sourceforge), and
> when the sourceforge site is back up, I'll add the feature requests,
> and assign them to myself.  I can't promise that I'll have much time
> to work on OBC, at least until another problem bugs me, but it doesn't
> hurt to be on the list, right?

Great. The email list is very low traffic normally (check the archive
for an idea of how low it's been recently), and most people just
contribute bits and pieces when they get time. Any and all help is
appreciated. I'll go sign you up.

Thanks again,

Boz

RE: [Onboardc-project] Defining Macros.

[Blake W. <bw...@la...>]

> On 9/4/05, Blake Winton <bw...@la...> wrote:
> > As I mentioned in a post to the Yahoo Group, I'm trying to compile
> > PalmCUnit with OnBoardC.  I ran into a bug dealing with macros with
> > empty argument lists, and posted a pseudo-patch which 
> > should have dealt with it.
> Thanks again for that, it's nice to have someone take the time to fix
> a problem for themself.

Heh.  That's what happens when my mailserver decides to stop working.
But surely you see more of that than other open-source projects, what
with all you users by definition knowing the language you used to write
the code.  :)

> > I worked around it for the time being by adding an ununsed dummy
> > argument, but now I'm running into another couple of 
> > missing features which are totally blocking me.
> I'd suggest removing the parens from the macro definition if no
> arguments are intended.

Well, yeah, I could do that, but I really want it to look like a
function call.  (It's the "FAIL()" pseudo-method in the Test Framework.)

> It would be nice to add these features. Could you add them as feature
> requests on the sourceforge page, so we can keep track of them?
> http://sourceforge.net/tracker/?atid=478289&group_id=55794

I will, but I might take a crack at them before I do.

> For the first one (concatenating string constants), take a look at
> compile.c, ~line 3009. (Search for DoubleQuote), which is where quoted
> strings are handled.
> 
> For the # preprocessor operator, you probably need to look at the
> macro argument expansion code, in OnBoardC.c (which you've already
> looked at it seems...)

Cool, I'll see what I can do in there, after I get it all set up.

> Again, we'd love to have you on the team, if you're interested in
> helping out by contributing.

I'm glad to submit patches when I can, but please don't put me on
the team.  I'm already on six or seven teams that I only submitted
a couple of patches to.  ;)

Ah, what the hell.  Add me (I think I'm bwinton on sourceforge), and
when the sourceforge site is back up, I'll add the feature requests,
and assign them to myself.  I can't promise that I'll have much time
to work on OBC, at least until another problem bugs me, but it doesn't
hurt to be on the list, right?

What else would you need to know?  My policy should be:
I-abstain-unless-I-officially-vote and I promise to abide by the rest
of the rules listed in section 3 of the Charter.

Thanks,
Blake.

Re: [Onboardc-project] Defining Macros.

[Steve L. <ste...@gm...>]

On 9/4/05, Blake Winton <bw...@la...> wrote:
> As I mentioned in a post to the Yahoo Group, I'm trying to compile
> PalmCUnit with OnBoardC.  I ran into a bug dealing with macros with
> empty argument lists, and posted a pseudo-patch which should have dealt
> with it.

Thanks again for that, it's nice to have someone take the time to fix
a problem for themself.

> I worked around it for the time being by adding an ununsed dummy
> argument, but now I'm running into another couple of missing features
> which are totally blocking me.

I'd suggest removing the parens from the macro definition if no
arguments are intended.

> The first is that pairs of string constants aren't concatenated, as per:
> http://eli-project.sourceforge.net/c_html/c.html#s6.1.4
> ("Sequences of string literals are translated as single strings.")

Hmm, yes, that needs fixing.

> I can mostly work around this by merging the strings by hand, but it
> presents a problem when we get to the second missing feature.  The
> preprocessor doesn't seem to implement the stringizing operator ("#"),
> as described here:
> http://msdn.microsoft.com/library/en-us/vclang/html/_predir_stringizing_o=
perator.asp
> or in section 6.10.3.2 of the ANSI C Standard at:
> http://www.nirvani.net.nyud.net:8090/docs/ansi_c.pdf

You're right, it doesn't. The preprocessor in OnBC is pretty minimal.
It would be nice to add these features. Could you add them as feature
requests on the sourceforge page, so we can keep track of them?

http://sourceforge.net/tracker/?atid=3D478289&group_id=3D55794

> Is there anyone working on these, or can someone give me some hints as
> to where in the code I would need to add these features?

The preprocessor isn't actually implemented as a seperate stage from
compiling/parsing, but is done as the parser goes over the code. As
such, there's a few places worth looking at.

For the first one (concatenating string constants), take a look at
compile.c, ~line 3009. (Search for DoubleQuote), which is where quoted
strings are handled.

For the # preprocessor operator, you probably need to look at the
macro argument expansion code, in OnBoardC.c (which you've already
looked at it seems...)

I'll try to take a look at these things unless you get to them first.
Adding them to the sourceforge Tracker will ensure they don't get
forgotten about, but I haven't had a lot of time for Palm work
recently.

Again, we'd love to have you on the team, if you're interested in
helping out by contributing.

Thanks,

Boz

[Onboardc-project] Defining Macros.

[Blake W. <bw...@la...>]

As I mentioned in a post to the Yahoo Group, I'm trying to compile 
PalmCUnit with OnBoardC.  I ran into a bug dealing with macros with 
empty argument lists, and posted a pseudo-patch which should have dealt 
with it.

I worked around it for the time being by adding an ununsed dummy 
argument, but now I'm running into another couple of missing features 
which are totally blocking me.

The first is that pairs of string constants aren't concatenated, as per:
http://eli-project.sourceforge.net/c_html/c.html#s6.1.4
("Sequences of string literals are translated as single strings.")
I can mostly work around this by merging the strings by hand, but it 
presents a problem when we get to the second missing feature.  The 
preprocessor doesn't seem to implement the stringizing operator ("#"), 
as described here:
http://msdn.microsoft.com/library/en-us/vclang/html/_predir_stringizing_operator.asp
or in section 6.10.3.2 of the ANSI C Standard at:
http://www.nirvani.net.nyud.net:8090/docs/ansi_c.pdf

Is there anyone working on these, or can someone give me some hints as 
to where in the code I would need to add these features?

Thanks,
Blake.

[Onboardc-project] Anyone have headers

[Tam H. <Ta...@gm...>]

Hi,
I just wanted to ask once again! Anyone who has headers to share?
Best regards
Tam Hanna

Re: [Onboardc-project] Header development

[John W. <or...@ru...>]

> Dear Developer comrades,
> it has finally become time to update the header IMHO. The dwelling of
> API headers, etc is not benefitial...
> John has assigned me the task to get the header maintained. And this
> is the point where I need your help. Please express your oppinions
> about the following questions either by email to the group or by
> emailing me directly!
> a)How should the header be organized? One big file, or a big file and
> small add-ins for example for Time manager, ....

I belive the best would be to to keep the OnBoardHeader.h with only small c=
hanges (together with necceraely updates) to the header family a bunch of a=
dditional headers: (e.g. SlotDrvrLib.h, VFSMgr.h, TelephonyMgr.h...) thus m=
aking it possible to add those API:s needed to your specific project. (also=
 making it an option to #include these additional headers if your device su=
ports them or not)

> b)What is a feasible max. size for the header thatis still acceptable
> and buildable on your development machines?

I belive it's 64kb (for the moment)

> c)What API's would you like to see added? Which definitions do you
> have sitting in API headers and would like to see them integrated?

We should aim for a complete set of API:s!
y
> d)Do you have some already-ported, skimmed API files that you want to
> share?=20

There are probably many users that have done these....
There is however  one, Peter Mo=F1ko, the man creating TbmpEdit and Woosh j=
ust to mention a few. We should ask him for his headers.

> I already have the SelectTime stuff, a PalmSource DIA header
> that works,  the launch codes and some other stuff!

I also belive we should leave the OS4.0 and try to make the headers work wi=
th OS5!
(e.g. OnBoardheader50.h)

> Best regards and thank you in advance for the help

It's my hope that as many developers as possible share thier thoughts upon =
this matter so please help us!

> Tam Hanna
/John

[Onboardc-project] Header development

[Tam H. <tam...@gm...>]

Dear Developer comrades,
it has finally become time to update the header IMHO. The dwelling of
API headers, etc is not benefitial...
John has assigned me the task to get the header maintained. And this
is the point where I need your help. Please express your oppinions
about the following questions either by email to the group or by
emailing me directly!
a)How should the header be organized? One big file, or a big file and
small add-ins for example for Time manager, ....
b)What is a feasible max. size for the header thatis still acceptable
and buildable on your development machines?
c)What API's would you like to see added? Which definitions do you
have sitting in API headers and would like to see them integrated?
d)Do you have some already-ported, skimmed API files that you want to
share? I already have the SelectTime stuff, a PalmSource DIA header
that works,  the launch codes and some other stuff!
Best regards and thank you in advance for the help
Tam Hanna
--=20
-------
http://tamspalm.blogspot.com

[Onboardc-project] Add stuff to header

[Tam H. <Ta...@gm...>]

Hi dudes,
I would like to add some stuff into the OBC distro. E.g. a file that
contains a list of features, a DIA header, etc. What must I observe? Is it
better to insert it into the header or into separate h files?
And sth else-the header misses a few types and api calls one needs every
day. Should I send them here?
Best regards
Tam Hanna

Re: [Onboardc-project] Small bug on OS2 in skeleton prog

[Nick G. <ko...@gm...>]

Oh, oops. My version. Well, the cookbook version has a tiny missing
thing, it says prefSize is a Int16, instead of a UInt16.

It's late :(

-Nick

On 5/15/05, John Wilund <or...@ru...> wrote:
> Nick,
>=20
> So this is true in OBC version number...?
>=20
> Since the startApp of the current version (2.5.1) is much more simple:
>=20
> startApp(){return;}
>=20
> and this, the latest skeleton, dosen't use preferences at all!
> Are you saying that this not current version skeleton OS2 BUG should be f=
ixed
>=20
> to what version?
>=20
> Thanks.
>=20
> /John
>=20
> > In the skeleton prog, in startApp(), I believe it says:
> >
> > Word prefSize;
> > if((PrefGetAppPreferences('....',1000,&prefs,&prefSize,true))=3D=3DnoPr=
eferencesFound......
> > or something of that sort. Well, on OS2 try loading the skeleton, exiti=
ng
> > (that doesn't just mean tapping applications, you have to go into anoth=
er
> > app for it to stop the first on OS2), and going back in. You should get=
 a
> > bus error. The problem is that prefSize is unititialized. It should rea=
d
> > Word prefSize =3D sizeof(Prefs);
> >
> > Also a Word is defined as an int, while prefSize is supposed to be a
> > UInt16*.
> >
> > These should be fixed so as not to set a bad example
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_ids93&alloc_id=16281&opclick
> _______________________________________________
> onboardc-project mailing list
> onb...@li...
> https://lists.sourceforge.net/lists/listinfo/onboardc-project
>

Re: [Onboardc-project] Small bug on OS2 in skeleton prog

[John W. <or...@ru...>]

Nick,

So this is true in OBC version number...?

Since the startApp of the current version (2.5.1) is much more simple:

startApp(){return;}

and this, the latest skeleton, dosen't use preferences at all!=20
Are you saying that this not current version skeleton OS2 BUG should be fix=
ed=20

to what version?

Thanks.

/John

> In the skeleton prog, in startApp(), I believe it says:
>=20
> Word prefSize;
> if((PrefGetAppPreferences('....',1000,&prefs,&prefSize,true))=3D=3DnoPref=
erencesFound......
> or something of that sort. Well, on OS2 try loading the skeleton, exiting=
=20
> (that doesn't just mean tapping applications, you have to go into another=
=20
> app for it to stop the first on OS2), and going back in. You should get a=
=20
> bus error. The problem is that prefSize is unititialized. It should read
> Word prefSize =3D sizeof(Prefs);
>=20
> Also a Word is defined as an int, while prefSize is supposed to be a=20
> UInt16*.
>=20
> These should be fixed so as not to set a bad example

[Onboardc-project] Small bug on OS2 in skeleton prog

[Nick G. <ko...@gm...>]

In the skeleton prog, in startApp(), I believe it says:

Word prefSize;
if((PrefGetAppPreferences('....',1000,&prefs,&prefSize,true))=3D=3DnoPrefer=
encesFound......
or something of that sort. Well, on OS2 try loading the skeleton, exiting=
=20
(that doesn't just mean tapping applications, you have to go into another=
=20
app for it to stop the first on OS2), and going back in. You should get a=
=20
bus error. The problem is that prefSize is unititialized. It should read
Word prefSize =3D sizeof(Prefs);

Also a Word is defined as an int, while prefSize is supposed to be a=20
UInt16*.

These should be fixed so as not to set a bad example

Re: [Onboardc-project] OnBoardHeader has 0 creation date

[Steve L. <ste...@gm...>]

Hi Nick,

On 5/12/05, Nick Guenther <ko...@gm...> wrote:
> Setting up OnBC on POSE the other day, when I installed OnBoardHeader
> it warned me that it has 0 for the creation date (which turns out to
> be sometime in 1932).=20

What version of the OnBoardHeader did you install?

> Am I the only one who has this? If not, we
> should, for correctness, fix it so it has a proper creation date.

I've not seen that problem before, and frequently use OnBoardHeader
under POSE. That said, I only ever use v40.

*shrug*

Boz

[Onboardc-project] OnBoardHeader has 0 creation date

[Nick G. <ko...@gm...>]

Setting up OnBC on POSE the other day, when I installed OnBoardHeader
it warned me that it has 0 for the creation date (which turns out to
be sometime in 1932). Am I the only one who has this? If not, we
should, for correctness, fix it so it has a proper creation date.

-Nick

[Onboardc-project] commit permission?

[Dennis R. <de...@bb...>]

Hello!  I just tried to commit roger.txt and was informed
that I didn't have write permission for the repository.  Did
I goof up the checkout (cvs co OnBoardC), or is there some
list somewhere that I need to be added to?  I have a bug
assigned to me, the code is checked out in my name, etc.

My sourceforge id is sfdennis.

Thanks!

Dennis Rockwell     de...@bb...
BBN Technologies    +1-617-873-5745
Cambridge, MA       +1-617-873-6091 (Fax)

Re: [Onboardc-project] newbie with a question

[Steve L. <ste...@gm...>]

Hi Dennis,

> To start with something easier, I looked at request 992781,
> bad double constants.  I have what I think will be a fix
> which includes octal constants but not scientific notation,
> but I'm troubled by the comment
>=20
>           // out-of-line because mwerks FP locals go nuts
>=20
> next to the function call that sucks up the fractional part
> of a float constant.  Can somebody clarify this?  Is there a
> compiler somewhere that screws up local floating point
> variables?

Well, it looks like the comment is referring to the Metrowerks Code
Warrior compiler, which OnBC was originally compiled with. The main
release is now compiled with prc-tools and CW is a few versions on
from where it was when that comment was probably added, so I'd guess
that we're fine now.

> If I can verify this fix, I'll grab PoC for this suggestion,
> the Jolly Roger for OnboardC.c (right?) and commit.

Thanks for volunteering to fix this. I've assigned the task to you. Go
ahead and check in your changes when you're ready.

Thanks,

Boz

PS - To grab the Roger, just update roger.txt and commit to cvs. There
aresome instructions in the file, or just ask if you have any
questions

[Onboardc-project] newbie with a question

[Dennis R. <de...@bb...>]

Hello!  I just signed up as a developer, intending to
improve the code generation.

To start with something easier, I looked at request 992781,
bad double constants.  I have what I think will be a fix
which includes octal constants but not scientific notation,
but I'm troubled by the comment

	   // out-of-line because mwerks FP locals go nuts

next to the function call that sucks up the fractional part
of a float constant.  Can somebody clarify this?  Is there a
compiler somewhere that screws up local floating point
variables?

If I can verify this fix, I'll grab PoC for this suggestion,
the Jolly Roger for OnboardC.c (right?) and commit.

Thanks!

Dennis Rockwell     de...@bb...
BBN Technologies    +1-617-873-5745
Cambridge, MA       +1-617-873-6091 (Fax)

[Onboardc-project] Beta tester

[Tam H. <Ta...@gm...>]

Hi,
I would also like to have the new beta!
Best regards
Tam Hanna

Re: [Onboardc-project] English (was Re: Hardkeys and the Cookbook)

[Wade G. <wa...@ad...>]

This is just for fun...

I wrote:

> I meant "steal" euphemistically.

So, after the fact, I looked-up euphemistically -- just to make sure I 
spelled it right.  I guess I'm so anal-retentive that I had to know but 
not so anal-retentive that I did it beforehand.  The funny thing is that 
the definition reads "An inoffensive expression that is substituted for 
one that is considered offensive."  Certainly, in this case, I did just 
the opposite.

I just thought that was funny (in an oddly ironic sort of way)...

-- 
Wade Guthrie
wa...@ad...

[Onboardc-project] Kudos to all

[Tam H. <Ta...@gm...>]

Hi,
I just want to chime in. OnBoardC is great!
Best regards
Tam Hanna

Re: [Onboardc-project] More Multiseg Progress

[Steve L. <ste...@gm...>]

On Tue, 05 Apr 2005 22:08 -0300, Peter Thorstenson <pe...@un...> wrote:
> Steve,
>
> The beta you sent me works just fine. It's magic! I'll be happy to make a
> new beta test if you want me to.

That'd be great. As luck would have it, I found another couple of bugs
last night, fixed one, but one remains. As soon as I get that one
fixed, I'll send the new version to the people who've been beta
testing so far.

I'll also update the documentation I'd produced to reflect the fact
that you no longer need segs.h or segs.c

> Thanks again for all the work you are putting into it.

Thanks for testing!

Boz

Re: [Onboardc-project] More Multiseg Progress

[Peter T. <pe...@un...>]

Steve,

...... Original Message .......
On Tue, 5 Apr 2005 01:19:53 +0100 Steve Little <ste...@gm...> 
wrote:
>Hi again,
>        Just to let people know that things are still progressing
>nicely. I've just finished implementing and debugging some code
>generation stuff to automatically open and lock all code segments when
>an app starts, and to unlock when it exits.
>
>I've also fixed various bugs that alpha testers have found. (Thank you all!)
>
>I need to do a bit more work on tidying up some of the code, some more
>testing, and need to start merging changes from the main branch ready
>for commiting to the main source tree.
>
>But it's basically all there and working (at last!), so I'm currently
>very happy!
>
>As soon as I've done a couple more tests myself, I'd really appreciate
>some help with beta testing this new version. Hopefully I'll have a
>version ready for testing by the end of the week.

The beta you sent me works just fine. It's magic! I'll be happy to make a 
new beta test if you want me to. Thanks again for all the work you are 
putting into it.
/Peter

Re: [Onboardc-project] More Multiseg Progress

[Nick G. <ko...@gm...>]

Yippee!!!!!!!!!!!!!!!!!!111oneoneonetwo

-Nick

On Apr 4, 2005 7:19 PM, Steve Little <ste...@gm...> wrote:
>=20
> Hi again,
> Just to let people know that things are still progressing
> nicely. I've just finished implementing and debugging some code
> generation stuff to automatically open and lock all code segments when
> an app starts, and to unlock when it exits.
>=20
> I've also fixed various bugs that alpha testers have found. (Thank you=20
> all!)
>=20
> I need to do a bit more work on tidying up some of the code, some more
> testing, and need to start merging changes from the main branch ready
> for commiting to the main source tree.
>=20
> But it's basically all there and working (at last!), so I'm currently
> very happy!
>=20
> As soon as I've done a couple more tests myself, I'd really appreciate
> some help with beta testing this new version. Hopefully I'll have a
> version ready for testing by the end of the week.
>=20
> Thanks,
>=20
> Boz
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=3D6595&alloc_id=3D14396&op=3Dclick
> _______________________________________________
> onboardc-project mailing list
> onb...@li...
> https://lists.sourceforge.net/lists/listinfo/onboardc-project
>

Re: [Onboardc-project] Hardkeys and the Cookbook

[John P. <jpy...@ca...>]

On Tuesday 05 April 2005 09:29 am, David Beers wrote:
> First of all, Johnny, it's been a while since I've thanked you for the
> careful, deliberate, and precise approach you bring to so many issues we
> discuss here. =A0I don't want to put words in anyone's mouth but I'll bet=
 I

Thank you for the very kind words.  I really appreciate everything you had =
to=20
say.

> My point about the endless discussions over what the GPL does and doesn't
> allow was just that it's not always easy to tell--or at least it often
> takes some real mental effort to tell--when something is ok or not if
> you're not in the practice of thinking about it a lot. =A0That's not a bad

I totally agree.  Again, my deepest apologies to everyone if I offended you=
=2E =20
I have always enjoyed being on this project.  I don't get the opportunity t=
o=20
work on the code these days, but do enjoy the frequent updates from John on=
=20
SrcEdit, wow what excellent work.  I also think the new multi-segment suppo=
rt=20
is off the hook.  These efforts are huge.  I have remained on the list,=20
because once in a blue moon I can actually contribute ;-) and by far the=20
people here are a great group of developers.

Johnny P
=2D-=20
Windows
Start Here
=46rustrating Hanging Crashing
Blue Screen of Death
Reboot