bezen...@gmail.com wrote:
> On Thursday, September 22, 2016 at 5:51:43 AM UTC+3, beze...@gmail.com
> wrote:
>> On Wednesday, September 21, 2016 at 10:09:25 PM UTC+3, Peter Otten wrote:
>> > bezen...@gmail.com wrote:
>> >
>> > > On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten
>>
On Thursday, September 22, 2016 at 5:51:43 AM UTC+3, beze...@gmail.com wrote:
> On Wednesday, September 21, 2016 at 10:09:25 PM UTC+3, Peter Otten wrote:
> > bezen...@gmail.com wrote:
> >
> > > On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten wrote:
> > >> bezen...@gmail.com wrote
On Wednesday, September 21, 2016 at 10:09:25 PM UTC+3, Peter Otten wrote:
> bezen...@gmail.com wrote:
>
> > On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten wrote:
> >> bezen...@gmail.com wrote:
> >>
> >> > On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten
> >> >
bezen...@gmail.com wrote:
> On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten wrote:
>> bezen...@gmail.com wrote:
>>
>> > On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten
>> > wrote:
>> >> bezen...@gmail.com wrote:
>> >>
>> >> > On Wednesday, September 21, 2016 a
On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten wrote:
> bezen...@gmail.com wrote:
>
> > On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten wrote:
> >> bezen...@gmail.com wrote:
> >>
> >> > On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten
> >> > w
On Wednesday, September 21, 2016 at 5:15:38 PM UTC+3, Peter Otten wrote:
> bezen...@gmail.com wrote:
>
> > On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten wrote:
> >> bezen...@gmail.com wrote:
> >>
> >> > On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten
> >> > w
bezen...@gmail.com wrote:
> On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten wrote:
>> bezen...@gmail.com wrote:
>>
>> > On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten
>> > wrote:
>> >> bezen...@gmail.com wrote:
>> >>
>> >> > After setting up csjark (http://cs
On Wednesday, September 21, 2016 at 4:43:47 PM UTC+3, beze...@gmail.com wrote:
> On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten wrote:
> > bezen...@gmail.com wrote:
> >
> > > On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten wrote:
> > >> bezen...@gmail.com wrote
On Wednesday, September 21, 2016 at 3:17:11 PM UTC+3, Peter Otten wrote:
> bezen...@gmail.com wrote:
>
> > On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten wrote:
> >> bezen...@gmail.com wrote:
> >>
> >> > After setting up csjark (http://csjark.readthedocs.io/), I'm trying to
> >
bezen...@gmail.com wrote:
> On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten wrote:
>> bezen...@gmail.com wrote:
>>
>> > After setting up csjark (http://csjark.readthedocs.io/), I'm trying to
>> > test on of my C header files which has following statements:
>> >
>> > typedef str
On Wednesday, September 21, 2016 at 1:14:14 PM UTC+3, Peter Otten wrote:
> bezen...@gmail.com wrote:
>
> > After setting up csjark (http://csjark.readthedocs.io/), I'm trying to
> > test on of my C header files which has following statements:
> >
> > typedef struct {
> >unsigned long X;
> >
bezen...@gmail.com wrote:
> After setting up csjark (http://csjark.readthedocs.io/), I'm trying to
> test on of my C header files which has following statements:
>
> typedef struct {
>unsigned long X;
>__int64 Y;
> } abc;
>
>
> If I'm changing __int64 to unsigned long I'm not getting th
12 matches
Mail list logo