octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Getting Tablicious on Octave Forge


From: Andrew Janke
Subject: Re: Getting Tablicious on Octave Forge
Date: Thu, 30 Jan 2020 15:13:21 -0500
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.1


On 1/30/20 1:44 PM, José Abílio Matos wrote:
> Thank you, that got me going.
>
> When installing I get several replicas of these errors:
>
> __oct_time_binsearch__.cc: In instantiation of ‘octave_idx_type* 
> binsearch(const T*, octave_idx_type, const T*, octave_idx_type) [with T = 
> double; octave_idx_type = int]’:
> __oct_time_binsearch__.cc:90:56:   required from here
> __oct_time_binsearch__.cc:51:79: warning: format ‘%lld’ expects argument of 
> type ‘long long int’, but argument 2 has type ‘octave_idx_type’ {aka ‘int’} [-
> Wformat=]

Any chance you're running a 32-bit Octave build? That's what I think
octave_idx_type being int indicates. That's an issue; Tablicious is
assuming 64-bit Octave here; I'll need to fiddle with it a bit to be
32-bit compatible, probably using #if or #ifdef macros so it picks the
conversion specifiers appropriately.
> warning: doc_cache_create: unusable help text found in file 'calendarDuration'
> warning: doc_cache_create: unusable help text found in file 'categorical'
> warning: doc_cache_create: unusable help text found in file 'datetime'
> warning: doc_cache_create: unusable help text found in file 'duration'
> warning: doc_cache_create: unusable help text found in file 'localdate'
> warning: doc_cache_create: unusable help text found in file 'missing'
> warning: doc_cache_create: unusable help text found in file 'string'
> warning: doc_cache_create: unusable help text found in file 'table'

These are benign. This is just because Octave's help function doesn't
support helptext in methods in classdef files, I think. The helptext is
still extracted so you can view it in the doc browser if you're using
the GUI.

Cheers,
Andrew





reply via email to

[Prev in Thread] Current Thread [Next in Thread]