lostgallifreyan wrote:
Jon A. Lambert jlamb...@oh.rr.com wrote:
(09/04/2009 09:57)
I never use the desktop as a file storage area
Ok, I'll bite. Storage? If that counts the temporay storage of moderately
sized files in a working session or two then yes, I use it for storage. I kind
of
KHMan keinh...@gmail.com wrote:
(09/04/2009 12:03)
At the end of the day, AFAIK the decision to pick patches for the
main trunk still lies with grischka. So why don't lostgallifreyan
push a suitable patch to the mob branch, or post it on this list.
It may go in, or it may not go in, but at
lostgallifreyan wrote:
When I hung around on a forum for a year or more I went from hunt-and-peck
typing to being near able to argue in realtime. One guy said he knew when
I was really incensed because the typographical error count dropped as
speed continued to rise. :) That aside, this IS the
Jon A. Lambert jlamb...@oh.rr.com wrote:
(09/04/2009 09:57)
As a long time windows user I've had no problems using tcc
I've never dragged and dropped files to a DOS box
I never use the desktop as a file storage area
Microsoft dropped support for DOS/win9x systems many years ago
What's odd about
Jon A. Lambert jlamb...@oh.rr.com wrote:
(09/04/2009 09:57)
I never use the desktop as a file storage area
Ok, I'll bite. Storage? If that counts the temporay storage of moderately
sized files in a working session or two then yes, I use it for storage. I kind
of thought that's what desktops
On Thursday 09 April 2009 13:17, lostgallifreyan wrote:
KHMan keinh...@gmail.com wrote:
(09/04/2009 12:03)
At the end of the day, AFAIK the decision to pick patches for the
main trunk still lies with grischka. So why don't lostgallifreyan
push a suitable patch to the mob branch, or post it
- Original Message -
From: lostgallifreyan lostgallifre...@gmail.com
To: tinycc-devel@nongnu.org
Sent: Thursday, April 09, 2009 1:17 PM
Subject: Re: [Tinycc-devel] Re: TCC:cannot find -lxyz.dll
KHMan keinh...@gmail.com wrote:
(09/04/2009 12:03)
At the end of the day, AFAIK
+eligis=wanadoo...@nongnu.org
[mailto:tinycc-devel-bounces+eligis=wanadoo...@nongnu.org] On Behalf Of Ivo
Sent: Thursday, April 09, 2009 18:18
To: tinycc-devel@nongnu.org
Subject: Re: [Tinycc-devel] Re: TCC:cannot find -lxyz.dll
On Thursday 09 April 2009 13:17, lostgallifreyan wrote:
KHMan keinh
: [Tinycc-devel] Re: TCC:cannot find -lxyz.dll
On Thursday 09 April 2009 13:17, lostgallifreyan wrote:
KHMan keinh...@gmail.com wrote:
(09/04/2009 12:03)
At the end of the day, AFAIK the decision to pick patches for the
main trunk still lies with grischka. So why don't lostgallifreyan
strcmp definitely does not use regular expressions!
With regards to file.c and file.C, although the Windows filesystem isn't case
sensitive, the build system (make, or scons, or just running the command
manually) passes the filenames to the compiler without losing case.
On Tuesday 07 April
Joshua Phillips jp.sittingd...@gmail.com wrote:
(08/04/2009 14:51)
strcmp definitely does not use regular expressions!
Oh? Never mind, if I remember right there can be strupper() on the incoming
sample of the file extension. Same thing would solve the .def extension case.
With regards to
Firstly, strupper isn't a C function, and I can't find anything about it in my
manpages.
Secondly, passing a filename to a program - the OS shouldn't interpret program
arguments, so if you run tcc foo.c, even if foo.c is actually called FOO.C,
tcc should still recognise it as a C file, try to
Joshua Phillips jp.sittingd...@gmail.com wrote:
(08/04/2009 17:56)
Firstly, strupper isn't a C function, and I can't find anything about it in my
manpages.
Strange.. I'm probably half-remembering an earlier version of Lua's current
string.upper() C will do what I need though, somehow. I'll
Drag-and-drop? O_o
For case-insensitive comparisons in C, there's strcasecmp (GNU) and stricmp
(MSVCRT). They're both identical in function, but are non-standard
extensions.
On Wednesday 08 April 2009 17:26:37 lostgallifreyan wrote:
Joshua Phillips jp.sittingd...@gmail.com wrote:
(08/04/2009
Joshua Phillips jp.sittingd...@gmail.com wrote:
(08/04/2009 18:36)
Drag-and-drop? O_o
Yep, drag and drop. :) Very useful. Open an 'Explorer' window to browse to
what-have-you, then drag it to a DOS window where it autowrites a path. So long
as those paths work, this is very fast and easy,
Ahh yes, so it isn't.
On Wednesday 08 April 2009 17:49:05 Ivo wrote:
On Wednesday 08 April 2009 19:36, Joshua Phillips wrote:
For case-insensitive comparisons in C, there's strcasecmp (GNU) and
stricmp (MSVCRT). They're both identical in function, but are
non-standard extensions.
lostgallifreyan wrote:
Yep, drag and drop. :) Very useful. Open an 'Explorer' window to browse
to what-have-you, then drag it to a DOS window where it autowrites a path.
Very useful?!? Sorry, but I really doubt your workflow.
Before I'd type tcc and then open an explorer and then grab
On Wed, Apr 08, 2009 at 06:55:12PM +0100, lostgallifreyan wrote:
Joshua Phillips jp.sittingd...@gmail.com wrote:
For case-insensitive comparisons in C, there's strcasecmp (GNU) and stricmp
(MSVCRT). They're both identical in function, but are non-standard
extensions.
No generic case
Dave Dodge dodo...@dododge.net wrote:
(08/04/2009 21:51)
No generic case comparion OR forcing in C?
Not for complete strings. There are case-folding functions for
individual characters, and you can trivially case-fold a string by
iterating over its content. Something like this, perhaps:
grischka gris...@gmx.de wrote:
(07/04/2009 18:18)
I'm not after complexity, just looking for the neatest way to
be sure that a newcomer can fire up TCC within about three
attempts at various optuions Windows offers. It;s when it
won't work after five or more that people run out of ideas
The behaviour of gcc, and therefore the behaviour, I suspect, of many other
projects trying to be as gcc-compatible as possible, interpret:
file.c - C source code which musd be preprocessed
file.cc, file.cp, file.cxx, file.cpp, file.CPP, file.c++, file.C - C++ source
code which must be
Joshua Phillips jp.sittingd...@gmail.com wrote:
(07/04/2009 21:55)
The behaviour of gcc, and therefore the behaviour, I suspect, of many other
projects trying to be as gcc-compatible as possible, interpret:
file.c - C source code which musd be preprocessed
file.cc, file.cp, file.cxx, file.cpp,
lostgallifreyan wrote:
grischka gris...@gmx.de wrote:
(04/04/2009 16:40)
As people seem consequently to ignore what's called readme.txt,
meybe we should just get rid of it and have some Windows section
in tcc-doc.html, respectively extend what's already there:
(5.3 PE-i386 file generation)
I
grischka gris...@gmx.de wrote:
(06/04/2009 19:48)
Separating Windows info from the rest I don't know about.. Might
be less daunting to make transitions if instead those things common
to all are placed first, to ease later changes. I think the
simplification of the quick start examples has
Small extra point to add to my last mail: It's worth stressing that the file
extensions on files passed to TCC must be lower case, as ti won't recognise
them as valid otherwise no matter how accurately the paths are written. In
Windows, a file called XYZ.C will often be displayed as Xyz.c which
lostgallifreyan wrote:
grischka gris...@gmx.de wrote:
No, I don't trust you. I just type
tcc hello_win.c
and it works. Why should we recommend horrible stuff like
DOS path and quoted full long name paths to newcomers?
Because that is what works in Windows. If it shouldn't be said
grischka gris...@gmx.de wrote:
(06/04/2009 23:06)
tcc hello_win.c
and it works. Why should we recommend horrible stuff like
DOS path and quoted full long name paths to newcomers?
Because that is what works in Windows. If it shouldn't be said as
a general thing, it can still be
An afterthough based on Lua, which might help to explain how this could work
for TCC...
If I write a Test File.lua in an arbitray location with the following line
inside it:
print(arg[1]) os.remove(arg[1])
... and I then make a new empty file on the destop 'New Text File.txt', I can
drag
Maybe Lua didn't actually do anything especially smart. :) Maybe TCC is doing
something smart, but limiting? If I knew C enough I'd try to find out but I can
only suggest things based on logic (and Occam's Razor) right now. Maybe TCC is
parsing paths too precisely according to limited
lostgallifreyan wrote:
Still, maybe -rdynamic needs more explanation with TCC. So please feel
free to suggest some addition to the docs, say, one short sentence,
placed to your choice ;)
I can try...
Perhaps somewhere in Quick start section, under the Here are some examples
to understand the
grischka gris...@gmx.de wrote:
(04/04/2009 16:40)
As people seem consequently to ignore what's called readme.txt,
meybe we should just get rid of it and have some Windows section
in tcc-doc.html, respectively extend what's already there:
(5.3 PE-i386 file generation)
I think that might partly
lostgallifreyan wrote:
Ok, I see that changing
C:\tcc\tcc.exe -I%P%\src -o%P%\bin\lua.dll -shared -rdynamic %P%\src\*.c
to
C:\tcc\tcc.exe -I%P%\src -o%P%\bin\lua.dll -shared -DLUA_BUILD_AS_DLL
%P%\src\*.c
..works as it should without changing the source itself, for Lua.exe anyway.
If I
grischka gris...@gmx.de wrote:
(03/04/2009 14:30)
Well see, Lua is a piece of code with some tens of thousands of lines
where each word is well designed and meaningful with the final binary
product. So if some symbols are exported and others are not then
this is likely not meant to fool
Extra point:
Actual TCC error is given literally as tcc: cannot find -lLua.dll
If I am being equally literal, I infer that maybe TCC is parsing it strangely
and actually thinks that not only is the -l switch an instruction to link some
file, but also, -l is taken literally as a prefix to as
lostgallifreyan wrote:
Extra point:
Actual TCC error is given literally as tcc: cannot find -lLua.dll
Actually there is the hello_dll example that you should try
first to see how linking with a DLL works.
===
To clarify:
TCC (like most other compiler on windows except GCC) cannot link
DLL's
grischka gris...@gmx.de wrote:
(02/04/2009 13:05)
lostgallifreyan wrote:
Extra point:
Actual TCC error is given literally as tcc: cannot find -lLua.dll
Actually there is the hello_dll example that you should try
first to see how linking with a DLL works.
===
To clarify:
TCC (like most
grischka gris...@gmx.de wrote:
(02/04/2009 13:05)
Tip:
There is the entire Win32-API in a single .hlp file available on the
LCC-WIN32 site:
http://www.cs.virginia.edu/~lcc-win32/
ftp://ftp.cs.virginia.edu/pub/lcc-win32/win32hlp.exe
Nice one. Thanks. Just what I want. Site seems to be down at
Ok, I think I found the answer myself after all.
For those who need to know, here it is:
(I hope that a mailing list archive stores this so others have an easier time
than I did.)
This method was prepared for TCC v0.9.24. Make this DOS batch file:
@ECHO OFF
SET P=C:\lua-5.1.4
IF NOT EXIST
grischka gris...@gmx.de wrote:
(03/04/2009 00:31)
lostgallifreyan wrote:
(Some explicit DLL-making and linking command examples in TCC's
tcc-doc.html 'Quick Start' section would be nice).
Well, it's in docs/readme.txt.
That only works if the .def file exists, my problem was I couldn't
39 matches
Mail list logo
