← Back to team overview

kicad-developers team mailing list archive

Re: kicad_pcb, kicad_mod format change for daily build?

 

Hi

I am just curious about this topic. Is this a case where we should have
bumped the SEXPR_BOARD_FILE_VERSION? Or is this not needed as an earlier
kicad version would read it just fine?

Nick

On Sun, 21 Apr 2019 at 18:46, Jeff Young <jeff@xxxxxxxxx> wrote:

> Hi Kevin,
>
> KiCad will read them in either way (quoted or un-quoted).
>
> KiCad has always written them out with quotes if they had spaces in them
> (so other tools have always needed to handle quotes).
>
> We’re just being more consistent now as there’s no justification for
> “saving a few characters” in this day and age (and going forward it will
> make things easier).
>
> Cheers,
> Jeff.
>
>
> > On 21 Apr 2019, at 17:25, Kevin Cozens <kevin@xxxxxxxxx> wrote:
> >
> >> On 15 Apr 2019, at 13:56, easyw <easyw@xxxxxxxxxxxx> wrote:
> >> recently I have noticed that both kicad_pcb and kicad_mod seems to have
> changed their format.
> >> It have been introduced double quotes for layers pads etc.
> > [snip]
> >> (layers
> >>    (0 F.Cu signal)
> >>    (31 B.Cu signal)
> >>
> >> (layers
> >>    (0 "F.Cu" signal)
> >>    (31 "B.Cu" signal)
> >
> > When I was asking about an updated file format document I was told
> "There have been virtually no changes to the file format other than how
> symbol library links are defined for a very long time."
> >
> > I consider it a file format change if quotes weren't needed before but
> they are now. It is the type of information I need to be sure I'm
> generating files in the proper format to avoid possibly having to go
> through the migration process.
> >
> > There may be other change(s) I may need to know about because the
> version number in the files has been bumped since the current file format
> doc was written. The files I'm generating are a version behind and have to
> go through a migration process when I try and open them. I don't fully
> trust the migration process.
> >
> > I hope someone can update the docs after KiCon, or perhaps someone can
> point me to which file(s) generate the schematic files used by eeschema.
> >
> > --
> > Cheers!
> >
> > Kevin.
> >
> > http://www.ve3syb.ca/               | "Nerds make the shiny things that
> > https://www.patreon.com/KevinCozens | distract the mouth-breathers, and
> >                                    | that's why we're powerful"
> > Owner of Elecraft K2 #2172          |
> > #include <disclaimer/favourite>     |             --Chris Hardwick
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>

Follow ups

References