On 8 Apr 2010, at 19:55 , [email protected] wrote:
Build Source Stamp: HEAD
Blamelist: eur.van.andel
OK, so here I am on the blamelist. Now what?
I updated svn and there is nothing in casualties?
ERROR: mcp3424.jal:Cannot find end of field content Description
OK. This is shown in the buildbot post as one of four attachments,
which I have to open separately. To be honest, I don't even know what
the end of field delimiter looks like.
Example:
-- Title: USART hardware control
-- Author: Stef Mientki, Copyright (c) 2002..2008, all rights
reserved.
-- Adapted-by: Sebastien Lelong, Someone Else
-- Compiler: >=2.4g
--
-- This file is part of jallib (http://jallib.googlecode.com)
-- Released under the BSD license (http://www.opensource.org/
licenses/bsd-license.php)
--
-- Description: Routines for sending and receiving through the PIC-
usart,
-- both RS232 and SPI are supported (for SPI see spi_hardware.jal)
-- Baudrate can simply be set through a human constant,
-- because the baudrate depending registers are calculated by this
unit.
-- Baudrate is calculated, starting at the high baudrate flag,
-- which will ensure the highest possible accuracy.
-- --
-- SPI routines are setup for more SPI-devices,
-- in which case CS should be controled outside this unit.
--
-- Sources: excellent article on USART: http://www.google.fr/search?
q=usart
--
-- Notes: an incredible note
--
http://code.google.com/p/jallib/wiki/JallibStyleGuide
So I assume this is just "--" on an empty line?
-- Title: mcp342, 18-bit, multi-channel delta-sigma AD converter
with I2C output
-- Author: Eur van Andel, [email protected] Copyright (c) 2010
-- Compiler: =2.4m
--
-- This file is part of jallib (http://jallib.googlecode.com)
-- Released under the ZLIB license (http://www.opensource.org/
licenses/zlib-license.html)
--
-- Description: this library works with the MCP3424 AD converter
from Microchip with up to 18 bits accuracy
-- Datasheet: DS22088B
--
-- Declare this in main program:
I have this two minus signs on an empty line? Maybe someone else
fixed it?
OK. I understand that jallib needs neat code and that it needs to be
checked. What I don't understand is that several people write page
long emails about this problem instead of fixing just TWO chars.
I work hard and as much as I love JAL, I don't have the time
(anymore) to discuss meta-JAL in this detail. If my errors are two
characters, it might be a lot easier to fix those than send me emails
about it or postings here.
About those emails: can you send me the headers of those? I can't
understand why they did not reach me.
And yes, the buildbot should email me directly on [email protected]. I
don't read [email protected] and I have tried several times to
remove the jallist mail overload from that account, to no avail.
---
ir EE van Andel [email protected] http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
