Have you consider that compiler searches its own header path and header files
have environment switches.
Make it clear where “mexPrintf” is defined and why it is not effective.
_
From: tinycc-devel-bounces+lifenjoiner=163@nongnu.org
[mailto:tinycc-devel-bounces+lifenjoiner=16
Hi there,
Character "0xFF" was found in file "COPYING", and it is hard to search the
meaning without a proper keyword. I guess it has some meaning for non-win
applications. Can anyone give an explanation? I am a win user, and view it by
notepad2.
Regards
___
Hi,
On 2014-06-27 19:51:37 +0800, YX Hao wrote:
> Character "0xFF" was found in file "COPYING", and it is hard to
> search the meaning without a proper keyword. I guess it has some
> meaning for non-win applications. Can anyone give an explanation?
> I am a win user, and view it by notepad2.
Ther
Hi Vincent Lefevre,
I got it with the hex view.
It is "0C" means form feed in "0A 0C 0A" showed "FF" with dark back color that
I made a misunderstanding.
Thanks!
>
> Hi,
>
> On 2014-06-27 19:51:37 +0800, YX Hao wrote:
> > Character "0xFF" was found in file "COPYING", and it is hard to
> > se
In addition,
>
> Hi Vincent Lefevre,
>
> I got it with the hex view.
>
> It is "0C" means form feed in "0A 0C 0A" showed "FF" with dark back color that
> I made a misunderstanding.
>
> Thanks!
>
> >
> > Hi,
> >
> > On 2014-06-27 19:51:37 +0800, YX Hao wrote:
> > > Character "0xFF" was found i
On 2014-06-27 21:32:06 +0800, YX Hao wrote:
> It is "0C" means form feed in "0A 0C 0A" showed "FF" with dark back
> color that I made a misunderstanding.
OK. I wonder why the FSF has put these Form Feed characters in this
file. Their other raw-text license files don't have them.
--
Vincent Lefèv
TCC is distributed with a file "COPYING", corresponding to the
Lesser GPL. This is incorrect. Such a file is normally called
"COPYING.LIB", and "COPYING" should contain the GPL. This is
important because some files are distributed under the GPL only:
il-opcodes.h
lib/libtcc1.c
texi2pod.pl
On 2014-06-27 21:56:39 +0800, YX Hao wrote:
> > > I think I've already seen such a bug with some software, probably
> > > because it wasn't detecting EOF (-1) correctly.
>
> Even if it is a "0xFF", it should not be the EOF, though many people
> say it. You can make a file to test using my attachme
Hi there,
I know this title sounds a bit egocentric but I thought some people might
wonder why I am not very present here since a few months. The reason is that I
recently joined a new company and they have a procedure to follow to be
authorized to participate to outside projects. It shouldn't
On Fri, Jun 27, 2014 at 5:06 PM, Thomas Preud'homme
wrote:
> I know this title sounds a bit egocentric but I thought some people might
>
FWIW, thanks and +1.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only gu
Stupid legal question. If TCC is GPL (rather than lesser GPL) and you
link with libtcc, then you would end up with software that was GPL. This
may be significant. Additionally, and start-up object files that TCC
generates may be considered "linking with tcc".
So ... anyone want to straighten
On 2014-06-27 11:30:54 -0500, Evan Langlois wrote:
> Stupid legal question. If TCC is GPL (rather than lesser GPL) and you
> link with libtcc, then you would end up with software that was GPL. This
> may be significant. Additionally, and start-up object files that TCC
> generates may be consid
On Fri, Jun 27, 2014 at 1:30 PM, YX Hao wrote:
> Have you consider that compiler searches its own header path and header
> files have environment switches.
>
>
>
> Make it clear where “mexPrintf” is defined and why it is not effective.
>
"mexPrintf" is defined in /usr/include/octave-3.8.1/octav
Hi,
> Markus Bergholz
> Sent: Saturday, June 28, 2014 2:55 AM
>
> On Fri, Jun 27, 2014 at 1:30 PM, YX Hao wrote:
>
>
> Have you consider that compiler searches its own header path and header
> files have environment switches.
>
^
Read the whole file and check
Le mardi 24 juin 2014, 23:06:50 David Mertens a écrit :
> Hey everyone,
>
>
> This, at least, is what I intended to do. I would appreciate if others
> could double-check that I performed the cherry picking and merging
> correctly. I do not perform this sort of work often.
Looks correct on my si
15 matches
Mail list logo
