CHICKEN 5.2.0 merged into OpenWRT master

[Jeronimo Pellegrini via]

Hello!

Thanks and congratulations to the Chicken team
for this new release!

Chicken 5.2.0 has been merged into OpenWRT master!
This time, there are two packages available:
- chicken-scheme-interpreter, containing csi only.
- chicken-scheme-full, containing the FULL Chicken
  system, including csc, feathers, chicken-install...

The second package requires gcc, but still possible to
install on wireless routers or other similar devices,
so long as there is enough storage space (for example, a
wireless router with the root filesystem on an external
pendrive).

Packages should be available on OpenWRT snapshots soon,
and if anything breaks, feel free to contact me!
(It is also possible to compile the packages for 
OpenWRT stable, should anyone want that)

J.

Re: tabular is not handling "" escapes

[Phil Bewig]

I have a CSV parser at my blog that might interest you:
https://programmingpraxis.files.wordpress.com/2013/01/textfiledatabases.pdf.
It properly handles bot Unix and DOS-style line endings, and embedded
quotes.

On Fri, Mar 6, 2020 at 2:00 PM Ivan Raikov  wrote:

> Hi Matt,
>
> Thanks, I think the default line terminator is the newline character,
> which would not work on files with DOS-style line endings. Could you
> call the reader with option eol: "\r\n" to see if this fixes the
> problem?
>
> -Ivan
>
> On Fri, Mar 6, 2020 at 11:24 AM Matt Welland 
> wrote:
> >
> > Thanks Ivan, I much appreciate the support.
> >
> > I tested 1.2 and it does solve the escaped quotes problem. I do now see
> another problem. Multi-line cells cause the parser some grief. The attached
> test.csv generated from Excel imports fine to gnumeric but fails with an
> "unable to parse record" with tabular.
> >
> > On Fri, Mar 6, 2020 at 8:16 AM Ivan Raikov 
> wrote:
> >>
> >> Hi Matt,
> >>
> >> Thank you for using tabular and for reporting this issue. This was
> >> indeed a bug in the code that handles escaped quotes. I have fixed it
> >> and have made a new release (1.2). Let me know if you run into any
> >> other issues. Best regards,
> >>
> >> -Ivan
> >>
> >> On Thu, Mar 5, 2020 at 2:14 PM Matt Welland 
> wrote:
> >> >
> >> > It is common in csv to escape double quotes with double quotes. This
> does not work in tabular and I was unable to figure out any other
> mechanism. Replacing the first " with \ did not work and neither did using
> single quotes around the string. Is there a built in mechanism? The csv
> files in question come from Microsoft Excel but I tested with a csv from
> Gnumeric and see the same problem.
> >> >
> >> > cat testing.csv
> >> > Junk,"Joe  ""Super"" Duper Guy",zsssy
> >> > "More Junk",1,2
> >> >
> >> > ../portit pp testing.csv
> >> >
> >> > Error: (list->string) bad argument type - not a character: (#\")
> >> >
> >> > Call history:
> >> >
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?
> >> > utf8-srfi-14.scm:101: iset#iset-contains?   <--
> >> >
> >> > Thanks.
> >> > --
> >> > Complexity is your enemy. Any fool can make something complicated.
> >> > It is hard to keep things simple. - Richard Branson.
> >
> >
> >
> > --
> > --
> > Complexity is your enemy. Any fool can make something complicated.
> > It is hard to keep things simple. - Richard Branson.
>
>

Re: tabular is not handling "" escapes

[Ivan Raikov]

Hi Matt,

Thanks, I think the default line terminator is the newline character,
which would not work on files with DOS-style line endings. Could you
call the reader with option eol: "\r\n" to see if this fixes the
problem?

-Ivan

On Fri, Mar 6, 2020 at 11:24 AM Matt Welland  wrote:
>
> Thanks Ivan, I much appreciate the support.
>
> I tested 1.2 and it does solve the escaped quotes problem. I do now see 
> another problem. Multi-line cells cause the parser some grief. The attached 
> test.csv generated from Excel imports fine to gnumeric but fails with an 
> "unable to parse record" with tabular.
>
> On Fri, Mar 6, 2020 at 8:16 AM Ivan Raikov  wrote:
>>
>> Hi Matt,
>>
>> Thank you for using tabular and for reporting this issue. This was
>> indeed a bug in the code that handles escaped quotes. I have fixed it
>> and have made a new release (1.2). Let me know if you run into any
>> other issues. Best regards,
>>
>> -Ivan
>>
>> On Thu, Mar 5, 2020 at 2:14 PM Matt Welland  wrote:
>> >
>> > It is common in csv to escape double quotes with double quotes. This does 
>> > not work in tabular and I was unable to figure out any other mechanism. 
>> > Replacing the first " with \ did not work and neither did using single 
>> > quotes around the string. Is there a built in mechanism? The csv files in 
>> > question come from Microsoft Excel but I tested with a csv from Gnumeric 
>> > and see the same problem.
>> >
>> > cat testing.csv
>> > Junk,"Joe  ""Super"" Duper Guy",zsssy
>> > "More Junk",1,2
>> >
>> > ../portit pp testing.csv
>> >
>> > Error: (list->string) bad argument type - not a character: (#\")
>> >
>> > Call history:
>> >
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?
>> > utf8-srfi-14.scm:101: iset#iset-contains?   <--
>> >
>> > Thanks.
>> > --
>> > Complexity is your enemy. Any fool can make something complicated.
>> > It is hard to keep things simple. - Richard Branson.
>
>
>
> --
> --
> Complexity is your enemy. Any fool can make something complicated.
> It is hard to keep things simple. - Richard Branson.

Re: tabular is not handling "" escapes

[Matt Welland]

Thanks Ivan, I much appreciate the support.

I tested 1.2 and it does solve the escaped quotes problem. I do now see
another problem. Multi-line cells cause the parser some grief. The attached
test.csv generated from Excel imports fine to gnumeric but fails with an
"unable to parse record" with tabular.

On Fri, Mar 6, 2020 at 8:16 AM Ivan Raikov  wrote:

> Hi Matt,
>
> Thank you for using tabular and for reporting this issue. This was
> indeed a bug in the code that handles escaped quotes. I have fixed it
> and have made a new release (1.2). Let me know if you run into any
> other issues. Best regards,
>
> -Ivan
>
> On Thu, Mar 5, 2020 at 2:14 PM Matt Welland 
> wrote:
> >
> > It is common in csv to escape double quotes with double quotes. This
> does not work in tabular and I was unable to figure out any other
> mechanism. Replacing the first " with \ did not work and neither did using
> single quotes around the string. Is there a built in mechanism? The csv
> files in question come from Microsoft Excel but I tested with a csv from
> Gnumeric and see the same problem.
> >
> > cat testing.csv
> > Junk,"Joe  ""Super"" Duper Guy",zsssy
> > "More Junk",1,2
> >
> > ../portit pp testing.csv
> >
> > Error: (list->string) bad argument type - not a character: (#\")
> >
> > Call history:
> >
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?
> > utf8-srfi-14.scm:101: iset#iset-contains?   <--
> >
> > Thanks.
> > --
> > Complexity is your enemy. Any fool can make something complicated.
> > It is hard to keep things simple. - Richard Branson.
>


-- 
--
Complexity is your enemy. Any fool can make something complicated.
It is hard to keep things simple. - Richard Branson.


test.csv
Description: MS-Excel spreadsheet

Re: CHICKEN 5.2.0 has been released

[Vasilij Schneidermann]

Hello Daniel,

> The sql-de-lite package has a small glitch.

This breaking change required adjustments in several eggs.  To our
knowledge all of them but sql-de-lite have been fixed by now.
Check out  for three
different ways to fix the issue.

Vasilij


signature.asc
Description: PGP signature

Re: tabular is not handling "" escapes

[Ivan Raikov]

Hi Matt,

Thank you for using tabular and for reporting this issue. This was
indeed a bug in the code that handles escaped quotes. I have fixed it
and have made a new release (1.2). Let me know if you run into any
other issues. Best regards,

-Ivan

On Thu, Mar 5, 2020 at 2:14 PM Matt Welland  wrote:
>
> It is common in csv to escape double quotes with double quotes. This does not 
> work in tabular and I was unable to figure out any other mechanism. Replacing 
> the first " with \ did not work and neither did using single quotes around 
> the string. Is there a built in mechanism? The csv files in question come 
> from Microsoft Excel but I tested with a csv from Gnumeric and see the same 
> problem.
>
> cat testing.csv
> Junk,"Joe  ""Super"" Duper Guy",zsssy
> "More Junk",1,2
>
> ../portit pp testing.csv
>
> Error: (list->string) bad argument type - not a character: (#\")
>
> Call history:
>
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?
> utf8-srfi-14.scm:101: iset#iset-contains?   <--
>
> Thanks.
> --
> Complexity is your enemy. Any fool can make something complicated.
> It is hard to keep things simple. - Richard Branson.