> So, could you, pretty please, point me to some nice C++ code.
Sorry, the work I did back then was not OSS. I'll have to write some
more "nice C++" for you :-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/l
Hi!
> Yes, that is a common complaint these days. I've written "nice C++"
> before, long before the C++ toolbox included all those messy new
> features that everyone just "had to use". I hate messy C++ too, but
> that doesn't stop me from wanting to use C++.
I always wanted to learn how to use C
> Also: What is the benefit in separating some features but still
> deliver it with the distribution?
We want people to be able to write their own private plugins. To do
so, they need a way to build them and keep them in sync with the pcb
sources.
__
Peter Clifton wrote:
> You could add it to PCB I guess - we could even teach PCB how to invoke
> the compiler and build plugins if we were feeling over-keen! (But
> perhaps that is encroaching on being too clever).
Also: What is the benefit in separating some features but still
deliver it with th
On Thu, Feb 24, 2011 at 01:29:08PM -0800, Colin D Bennett wrote:
> On Thu, 24 Feb 2011 20:48:39 +
> Peter Clifton wrote:
> > You could add it to PCB I guess - we could even teach PCB how to
> > invoke the compiler and build plugins if we were feeling over-keen!
> > (But perhaps that is encroac
On Thu, 24 Feb 2011 20:48:39 +
Peter Clifton wrote:
> On Thu, 2011-02-24 at 15:45 -0500, DJ Delorie wrote:
> > > In-tree "plugins" is a +1 from me, as I hate to think of the
> > > level of breakage we could cause if we do more drastic
> > > re-factoring of PCB.
> >
> > I was thinking, pcb pr
On Thu, 2011-02-24 at 15:45 -0500, DJ Delorie wrote:
> > In-tree "plugins" is a +1 from me, as I hate to think of the level of
> > breakage we could cause if we do more drastic re-factoring of PCB.
>
> I was thinking, pcb probably will end up needing a command line option
> to print the right comp
> In-tree "plugins" is a +1 from me, as I hate to think of the level of
> breakage we could cause if we do more drastic re-factoring of PCB.
I was thinking, pcb probably will end up needing a command line option
to print the right compiler options to build plugins with...
especially with the opti
I think C++ would be much more maintainable if they removed the
"class", "friend", and "template" keywords.
Maybe I'll #define those to something nasty in the pcb sources. ;-)
Now if only there were a "multiple_inheritance" keyword I could
poison...
On Thu, 2011-02-24 at 10:32 -0800, Ben Jackson wrote:
> On Thu, Feb 24, 2011 at 03:28:10PM +, Peter Clifton wrote:
> >
> > I think if we continue with plugins the way we do, we need some API to
> > advertise an API version, and means for plugins to load (or fail to
> > load) based upon compati
On Thu, 2011-02-24 at 09:44 -0700, John Doty wrote:
> Too many modern programmers don't understand the distinction between
> abstraction and obfuscation. When pressed on this point, they will
> insist that they do understand, and then continue to demonstrate by
> their actions that they do not. Th
On Thu, Feb 24, 2011 at 03:28:10PM +, Peter Clifton wrote:
>
> I think if we continue with plugins the way we do, we need some API to
> advertise an API version, and means for plugins to load (or fail to
> load) based upon compatibility with a given version.
It's funny that those plugins brok
> I am sorry, but I have never seen "nice C++".
Yes, that is a common complaint these days. I've written "nice C++"
before, long before the C++ toolbox included all those messy new
features that everyone just "had to use". I hate messy C++ too, but
that doesn't stop me from wanting to use C++.
On Thu, Feb 24, 2011 at 11:51:30AM -0500, DJ Delorie wrote:
>
> > I'd not constrain ourselves to one action per file, but certainly
> > breaking things down by topic would be a good idea.
>
> Perhaps one file per action for stand-alone actions, and one file per
> group named after the group's com
On Thu, Feb 24, 2011 at 11:56:04AM -0500, DJ Delorie wrote:
>
> > I've been debugging some problems in a large 3D CAD + FEA system written
> > in C++ recently. Give me nice C code that ANY day over that impenetrable
> > crap.
>
> I'd rather have nice C++ code than either nice C code or crappy C++
> I've been debugging some problems in a large 3D CAD + FEA system written
> in C++ recently. Give me nice C code that ANY day over that impenetrable
> crap.
I'd rather have nice C++ code than either nice C code or crappy C++ code.
___
geda-user maili
> I'd not constrain ourselves to one action per file, but certainly
> breaking things down by topic would be a good idea.
Perhaps one file per action for stand-alone actions, and one file per
group named after the group's common action prefix for groups. I.e:
teardrops.c for Teardrops()
but
e
On Feb 24, 2011, at 8:50 AM, Peter Clifton wrote:
> On Thu, 2011-02-24 at 08:38 -0700, John Doty wrote:
>> On Feb 24, 2011, at 8:22 AM, Peter Clifton wrote:
>>
>>> Means C didn't find the function, and it assumes it returns integer in
>>> that case. Dumb convention IMO.
>>
>> "C is quirky, flaw
On Thu, Feb 24, 2011 at 09:23:44AM -0700, Russell Dill wrote:
> On Thu, Feb 24, 2011 at 8:50 AM, Peter Clifton wrote:
> > On Thu, 2011-02-24 at 08:38 -0700, John Doty wrote:
> >> On Feb 24, 2011, at 8:22 AM, Peter Clifton wrote:
> >> > Means C didn't find the function, and it assumes it returns in
On Thu, Feb 24, 2011 at 10:24:07AM -0500, DJ Delorie wrote:
>
> > Yes, it is. We should probably keep some plugins with the PCB source and
>
> I was thinking a src/actions/ subdirectory, with one file per action
> named after the action, where we can both import plugins and segregate
> core actio
On Thu, Feb 24, 2011 at 8:50 AM, Peter Clifton wrote:
> On Thu, 2011-02-24 at 08:38 -0700, John Doty wrote:
>> On Feb 24, 2011, at 8:22 AM, Peter Clifton wrote:
>>
>> > Means C didn't find the function, and it assumes it returns integer in
>> > that case. Dumb convention IMO.
>>
>> "C is quirky, f
On Thu, 2011-02-24 at 08:38 -0700, John Doty wrote:
> On Feb 24, 2011, at 8:22 AM, Peter Clifton wrote:
>
> > Means C didn't find the function, and it assumes it returns integer in
> > that case. Dumb convention IMO.
>
> "C is quirky, flawed, and an enormous success." - Dennis M. Ritchie.
True..
On Feb 24, 2011, at 8:22 AM, Peter Clifton wrote:
> Means C didn't find the function, and it assumes it returns integer in
> that case. Dumb convention IMO.
"C is quirky, flawed, and an enormous success." - Dennis M. Ritchie.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
j.
On Thu, 2011-02-24 at 10:24 -0500, DJ Delorie wrote:
> > Yes, it is. We should probably keep some plugins with the PCB source and
>
> I was thinking a src/actions/ subdirectory, with one file per action
> named after the action, where we can both import plugins and segregate
> core actions into se
On Wed, 2011-02-23 at 21:04 -0800, Ben Jackson wrote:
> On Thu, Feb 24, 2011 at 05:01:33AM +0100, Kai-Martin Knaak wrote:
> > Mark Rages wrote:
> >
> > > License allowing, can you please post the fixed plugins somewhere?
> >
> > The necessary modifications are simple one-liners.
> > Both are plug
> > Changelog says... nothing! :-P
>
> Don't we auto generate that on release from the git history? (Too busy
> to check right now!)
Yup. I was just checking the usual suspects.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.o
> Yes, it is. We should probably keep some plugins with the PCB source and
I was thinking a src/actions/ subdirectory, with one file per action
named after the action, where we can both import plugins and segregate
core actions into separate files for maintenance.
__
On Wed, 2011-02-23 at 21:52 -0500, DJ Delorie wrote:
> Changelog says... nothing! :-P
Don't we auto generate that on release from the git history? (Too busy
to check right now!)
--
Peter Clifton
Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Av
On Thu, 2011-02-24 at 03:48 +0100, Kai-Martin Knaak wrote:
> Hi.
>
> I'd love to use the smartdisperse plugin by Ben Jackson for my
> current project (component count 1755). Compile was fine except
> for one of these pointer warnings c is infamous for:
> /---
> $ gcc -I /usr/local/p
On Thu, Feb 24, 2011 at 05:01:33AM +0100, Kai-Martin Knaak wrote:
> Mark Rages wrote:
>
> > License allowing, can you please post the fixed plugins somewhere?
>
> The necessary modifications are simple one-liners.
> Both are plugins are GPL, so here you go:
> http://lilalaser.de/tmp/smartdi
Mark Rages wrote:
> License allowing, can you please post the fixed plugins somewhere?
The necessary modifications are simple one-liners.
Both are plugins are GPL, so here you go:
http://lilalaser.de/tmp/smartdisperse.c
http://lilalaser.de/tmp/teardrops.c
> Also, while on the su
DJ Delorie wrote:
> The policy is that we allow anyone to write plugins for their own use,
> and if they want to share them, they may. I see no reason to require
> authors to contribute their plugins to the core pcb code if they do
> not wish to.
So it is up to the authors. Coincidentally, you a
On Wed, Feb 23, 2011 at 9:29 PM, Kai-Martin Knaak wrote:
> DJ Delorie wrote:
>
>> The extra parameter is a string to use to tag the call, for debugging.
>> Just omit it.
>
> Thanks!
> Now, the plugin works (and your teardrops plugin, too).
License allowing, can you please post the fixed plugins s
> The policy is that we allow anyone to write plugins for their own use,
> and if they want to share them, they may. I see no reason to require
> authors to contribute their plugins to the core pcb code if they do
> not wish to.
I don't want to /require/ anyone to do anything :) Both plugins are
DJ Delorie wrote:
> The extra parameter is a string to use to tag the call, for debugging.
> Just omit it.
Thanks!
Now, the plugin works (and your teardrops plugin, too).
---<)kaimartin(>---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffentlicher PGP-Schlüssel:
http://pool.sks-keyservers.n
The extra parameter is a string to use to tag the call, for debugging.
Just omit it.
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
DJ Delorie wrote:
> 1. Replace all calls to MyCalloc() with calls to calloc()
It is not that easy.
MyCalloc() has three arguments but calloc() just asks for two.
Meaning, I'll have to understand the code... =:)
---<)kaimartin(>---
--
Kai-Martin Knaak
Email: k...@familieknaak.de
Öffent
> This raises a question for me - should these plugins be incorporated
> into PCB head ?
Maybe, maybe not.
> These plugins were written before I joined this list, has the
> rationale for keeping them separate vs. incorporating them into head
> been thoroughly discussed ?
The policy is that we a
So DJ's teardrop plugin and Ben Jackson's smartdisperse plugin are now
both broken because of changes made to PCB head in the last few
months.
This raises a question for me - should these plugins be incorporated
into PCB head ?
These plugins were written before I joined this list, has the
rationale
Changelog says... nothing! :-P
git says...
commit 0c62fca0df9bd9ebe7bedfbee0af3502e4298a42
Author: Peter Clifton
Date: Tue Dec 7 01:47:28 2010 +
Remove My* memory allocation routines. Just use the standard APIs directly
This means the following changes:
1. Repl
40 matches
Mail list logo
