Mailinglist Archive: yast-devel (51 mails)
| < Previous | Next > |
Re: [yast-devel] how to mark *.ybc file outdated?
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 14 Sep 2007 12:02:41 +0200
- Message-id: <20070914100241.GA30328@xxxxxxxxxxxxx>
* Stefan Hundhammer <sh@xxxxxxx> [Sep 14. 2007 11:51]:
> On Friday 14 September 2007 09:52, Johannes Meixner wrote:
> [...byte code files outdated...]
>
>
> I've been wondering for a long time if we shouldn't seriously consider to
> handle the byte code the same way Perl does: Byte-compile "on the fly" and
> keep the byte code just in memory, never write it to disk. IMHO this would
> make handling YCP code _much_ easier.
What are the problems with the current way of pre-compiling exactly ?
How to deal with syntax errors resulting in a failed load ?
I'd also like to know more about the size of the mentioned problem.
Whats the effect on the customer when module compilation is done on-the fly ?
Whats the effect on the developer ?
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
> On Friday 14 September 2007 09:52, Johannes Meixner wrote:
> [...byte code files outdated...]
>
>
> I've been wondering for a long time if we shouldn't seriously consider to
> handle the byte code the same way Perl does: Byte-compile "on the fly" and
> keep the byte code just in memory, never write it to disk. IMHO this would
> make handling YCP code _much_ easier.
What are the problems with the current way of pre-compiling exactly ?
How to deal with syntax errors resulting in a failed load ?
I'd also like to know more about the size of the mentioned problem.
Whats the effect on the customer when module compilation is done on-the fly ?
Whats the effect on the developer ?
Klaus
---
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx
| < Previous | Next > |