Hi Seb,
On 12/03/11 09:28 am, Sebastien Lelong wrote:
I got the reason why it doesn't work, but no fix at the moment without
big changes.
It appears your procs are defined on two lines, whereas jalapi scans
code, *line by line*, and expect a procedure definition in one single
line... ("is" at EOL)
As I said, I'd need to review all jalapi in order to fix this, I would
prefer to spend my time elsewhere :) When I get a chance, I'll dive into
this again.
OK! I understand a fix may take some time.
In my opinion missing documentation is worse than the inconvenience of
long source lines. So maybe I should reflow splitted procedure
declarations such that the complete declaration is on 1 line.
Not a big deal for this particular library (glcd_common.jal) , but there
maybe many more occurrences of splitted procedures/fuctions
declarations! So a fix in the docs generation process would be welcome!
Is it complicated to collect multi-line procedure/function declarations
in a single string before parsing?
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
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.
