[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP355FD798836344983E9FA71FD2D0@phx.gbl>
Date: Tue, 15 Jan 2013 21:06:44 +0100
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: FMT_MAIN_VERSION changes (was: --list= handling moved out of john.c)
On 01/15/2013 08:56 PM, magnum wrote:
> On 15 Jan, 2013, at 20:27 , Frank Dittrich <frank_dittrich@...mail.com> wrote:
>> 2.
>> Should we enhance listconf_list_method_names() to include "source" for
>> FMT_MAIN_VERSION > 9?
>> Function listconf_parse_late() would need to be enhanced as well, to
>> handle "source" for FMT_MAIN_VERSION > 9.
>>
>> Then, it should work for bleeding-jumbo as well.
>
>
> There is no point in committing any such thing to unstable but we could do it to bleeding. Then we'd need no ifdefs for that matter. By the way, bleeding will soon have FMT_MAIN_VERSION 11.
Are the changes intended for FMT_MAIN_VERSION 11 (compared to 10)
discussed or listed somewhere?
Can additional changes be suggested until FMT_MAIN_VERSION is changed to 11?
I thought about including __FILE__ somewhere, may be directly, or via
another definition somewhere else in a format definition file (e.g.,
close to the fmt_tests structure definition) which then refers to
__FILE__. This would make it easier to locate the source code which
implements a particular format I am interested in...
Frank
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
